meta_ads_get_pixel_health
Get Meta Pixel Health
Description
Comprehensive pixel health check: metadata, CAPI connection status, event volume stats, automatic matching config, and diagnostic checks (including event match quality indicators). capi.connected is true when an active CAPI Gateway config exists or server events were observed in the lookback window (capi.server_event_count), false when both signals were readable and showed neither, and "unknown" when the signals could not be read — NEVER report CAPI as disconnected when it is "unknown"; tell the user to verify in Meta Events Manager instead. Use this to diagnose tracking issues before analyzing ad performance — low ROAS could be a tracking problem, not a campaign problem. When event_stats_status is "permission_denied", surface event_stats_message to the user — the rest of the pixel health audit is still valid.
Usage
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "meta_ads_get_pixel_health",
"arguments": {
"account_id": "act_123",
"reason": "Audit tracking setup"
}
}
}
hopkin meta pixel-health get
| Flag | Type | Required | Description |
|---|---|---|---|
--account | string | Required | The ad account ID (with or without act_ prefix) |
--pixel-id | string | Optional | Specific pixel ID to check. If omitted, checks all pixels on the account. |
--event-names | array | Optional | Filter event stats to these event names (e.g. ["Purchase", "Lead"]) |
--days-back | integer | Optional | Number of days of event stats to include (default: 28, max: 90) |
--limit | integer | Optional | Max pixels per page (default: 5, max: 20) |
--cursor | string | Optional | Pagination cursor from previous response |
{
"mcpServers": {
"meta-ads": {
"url": "https://meta.mcp.hopkin.ai",
"transport": "sse"
}
}
}
- All pixels for account
- Specific pixel
- Filter to key events
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
account_id |
string |
Required | The ad account ID (with or without act_ prefix)minLength: 1 |
reason |
string |
Required | Why this tool call is neededminLength: 1, maxLength: 500 |
Optional parameters (5)
| Name | Type | Required | Description |
|---|---|---|---|
pixel_id |
string |
Optional | Specific pixel ID to check. If omitted, checks all pixels on the account.minLength: 1 |
event_names |
array |
Optional | Filter event stats to these event names (e.g. ["Purchase", "Lead"]) |
days_back |
integer |
Optional | Number of days of event stats to include (default: 28, max: 90)min: 1, max: 90 |
limit |
integer |
Optional | Max pixels per page (default: 5, max: 20)min: 1, max: 20 |
cursor |
string |
Optional | Pagination cursor from previous responseminLength: 1 |
Examples
All pixels for account
{
"account_id": "act_123",
"reason": "Audit tracking setup"
}
hopkin meta pixel-health get --account act_123
Specific pixel
{
"account_id": "act_123",
"pixel_id": "456",
"reason": "Check pixel firing status"
}
hopkin meta pixel-health get --account act_123 --pixel-id 456
Filter to key events
{
"account_id": "act_123",
"event_names": [
"Purchase",
"Lead"
],
"days_back": 7,
"reason": "Check tracking health for key events"
}
hopkin meta pixel-health get --account act_123 --event-names Purchase,Lead --days-back 7