Meta Ads by Get MCP Ads

meta get delivery diagnostics

meta_get_delivery_diagnostics

Read-onlyIdempotent

Retrieve aggregate delivery diagnostics for campaigns, ad sets, and ads, surfacing status issues and simple performance insights for your ad account.

Instructions

Aggregate read-only delivery diagnostics across campaigns, ad sets, and ads using status/effective_status/issues_info where available plus simple delivery insights.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`level`	No	Entity or aggregation level for the requested report.	all
`limit`	No	Maximum number of returned items or rows. The declared bounds and default apply; use pagination for additional results.
`cursor`	No	Pagination cursor from previous response
`timeRange`	No	Optional custom insights date range.
`datePreset`	No	Insights date preset for simple delivery metrics. Defaults to last_7d.
`adAccountId`	Yes	Ad account ID (e.g., act_123456789)
`effectiveStatusFilter`	No	Optional effective_status filter values such as ACTIVE, PAUSED, WITH_ISSUES, DISAPPROVED.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Sep 23, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly, openWorld, and idempotent annotations, it adds that data is aggregated across levels and that diagnostics depend on status/effective_status/issues_info 'where available.' This communicates partial data availability and non-raw aggregation behavior. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, starting with the key verb and scope. The later clause is dense but acceptable; it could be split for readability without changing substance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With full parameter descriptions, an output schema, and safety annotations, the remaining burden is selection context, which the 'delivery diagnostics' scope mostly covers. It could add explicit alternatives or caveats about pagination and data availability, but schema and annotations already carry much of the load.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all seven parameters. The description adds light context by mapping 'status/effective_status/issues_info' to diagnostic fields and 'simple delivery insights' to date/time filtering, but it does not materially extend schema semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('aggregate') and resource ('delivery diagnostics') with explicit scope across campaigns, ad sets, and ads. The phrase 'delivery diagnostics' clearly differentiates it from sibling reporting tools like meta_get_insights or meta_health_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for read-only delivery health aggregation but gives no explicit when-to-use or when-not-to-use guidance. It does not name alternatives or selection conditions, so an agent must infer usage from the phrase 'delivery diagnostics.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server