Skip to main content
Glama

Ads Uploader: Meta Ads MCP

Estimate Audience and Delivery

ads_estimate_delivery
Read-onlyIdempotent

Answer “how big is this audience”: read Meta reach and delivery estimates for AdSpec targeting and an optimization goal. Does not create ads. Estimates are predictions, not guaranteed delivery. A 429 carries Retry-After. ROW_QUOTA_EXCEEDED carries the time the quota resets (meta.quota.resetsAt).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>",
      "targeting": "<targeting>",
      "optimizationGoal": "<optimizationGoal>"
    },
    "name": "ads_estimate_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass the read cache.
accountIdYesAd account ID.
targetingYesAdSpec targeting shape, converted by the ad-creation builder. Include at least one location. No inherited source targeting is available for estimates.
promotedObjectNo
optimizationGoalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are predictions rather than guaranteed delivery, plus concrete failure semantics (429 with Retry-After, ROW_QUOTA_EXCEEDED with meta.quota.resetsAt) that the agent can act on when retrying.

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?

Four short sentences, all load-bearing, with the core purpose and the read-only scope front-loaded. The error-code sentences are dense but actionable rather than filler; the only redundancy is the title restated in the first clause.

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?

No output schema exists, so the description is right to emphasize input requirements and error handling, and the prediction caveat sets expectations for the numbers returned. It could say a bit more about what the estimate response contains (reach range vs. delivery figures), which is the one real gap for a tool whose whole output is the payload.

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?

With 60% schema coverage the schema carries most of the meaning, and the description only echoes that AdSpec targeting and an optimization goal are required. It adds nothing about the sizeable nested targeting object, the promotedObject field, or the cache-bypassing fresh flag beyond what the schema already states.

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 and resource ("read Meta reach and delivery estimates") with the exact inputs that drive it (AdSpec targeting, optimization goal), and frames the user question it answers. It also explicitly excludes a nearby sibling behavior with "Does not create ads," so the agent can separate it from ads_create without opening a schema.

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

Usage Guidelines4/5

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

The opening phrase "Answer 'how big is this audience'" gives a clear situation for use, and "Does not create ads" marks the boundary against creation tools. It stops short of naming an alternative for planning-time estimates or stating prerequisites such as the need for a fully built targeting spec, but the intended context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.