Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_delivery_estimate

Estimate an ad set's delivery and daily reach to plan campaign performance using its ad set ID and optional optimization goal.

Instructions

Get delivery estimate for an ad set, including estimated daily reach. Note: the delivery_estimate edge exists on the ad set (and ad account) node, not on individual ads. Also note: as of v26.0, the daily_outcomes_curve, budget_guardrail, and estimate_dau fields are no longer returned (removed with no replacement).

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": {
      "adset_id": "<adset_id>"
    },
    "name": "get_delivery_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
adset_idYesAd Set ID
optimization_goalNoOptimization goal to estimate for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.6.1
    • removedInput schema / properties / ad_id
      Removed value: -{
-  "description": "Ad ID",
-  "type": "string"
-}
    • addedInput schema / properties / adset_id
      Added value: +{
+  "description": "Ad Set ID",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "ad_id"
-]New value: +[
+  "adset_id"
+]
  2. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does add real value: it discloses the v26.0 removal of daily_outcomes_curve, budget_guardrail, and estimate_dau. That said, it omits auth/permission requirements, rate-limit or cost behavior, and the overall shape of what remains in the response.

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?

Purpose is front-loaded in the first clause, followed by two clearly marked caveats. It is appropriately sized and every sentence earns its place, though the two 'Note:' blocks are slightly repetitive in framing.

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?

For a read-only, two-parameter tool with no output schema, the description usefully sets expectations about node scope and version-dependent field removal. Auth requirements and remaining return shape are still unaddressed, but the critical caveats an agent needs are present.

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 adset_id and optimization_goal are already documented in the schema; the baseline is 3. The description implies the ad-set scope but adds no syntax, format, or allowed-value detail beyond the schema.

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

Purpose4/5

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

States a specific verb and resource ('Get delivery estimate for an ad set') plus the scope of what is returned ('estimated daily reach'). The note that the delivery_estimate edge lives on the ad set/ad account node, not on individual ads, helps separate it from ad-level siblings, but the closely-named sibling get_reach_estimate is never addressed.

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 node-scope note implies when this is applicable (ad set / ad account, not individual ads), which is useful routing guidance. However, it never names or contrasts the obvious alternative (get_reach_estimate) or states any prerequisites, leaving the when-to-use decision partly to inference.

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

Deploy Server

Other Tools