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

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_reach_estimate

Estimate audience reach for a targeting spec to plan ad campaigns. Use before creating campaigns to gauge potential audience size.

Instructions

Get estimated audience reach for a given targeting specification. Useful for planning campaigns before creating them.

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": {
      "targeting_spec": "<targeting_spec>"
    },
    "name": "get_reach_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoAd account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.
targeting_specYesJSON string of targeting spec (same format as ad set targeting)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.1
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Ad account ID to query (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. Beyond the implied read-only nature of 'Get', it says nothing about permissions, rate limits, latency/cost of an estimate call, or whether results are cached — significant gaps for a tool with zero annotation coverage.

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

Conciseness5/5

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

Two short sentences with zero padding, and the core purpose is front-loaded ahead of the planning use case. Nothing needs trimming.

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

Completeness3/5

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

With no output schema and no annotations, the description should carry more weight, but it never explains what the estimate returns (e.g. reach numbers, breakdowns) or how it differs from get_delivery_estimate. Adequate to call the tool, but incomplete for confident selection.

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 both parameters (account_id with its env-var fallback and targeting_spec) are already fully documented in the schema. The description adds no syntax or format detail beyond restating 'targeting specification', so the baseline 3 applies.

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 ('Get') and resource ('estimated audience reach') scoped to a targeting specification, which is far more than a tautology. However, it fails to distinguish itself from the very close sibling get_delivery_estimate, which an agent would plausibly confuse it with.

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?

'Useful for planning campaigns before creating them' implies a usage context (pre-flight planning), which is genuine but vague. It gives no explicit when-to-use or when-not-to-use guidance and never names get_delivery_estimate as the alternative for a different estimation task.

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