Skip to main content
Glama

Estimate a Meta audience

ads_estimate_reach
Read-only

Estimate how many people a Meta targeting spec reaches, before creating a campaign or changing an ad set's targeting. Creates nothing. lower and upper are null when Meta cannot estimate.

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": {
      "adAccountId": "<adAccountId>",
      "targeting": "<targeting>"
    },
    "name": "ads_estimate_reach"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNometa_ads, tiktok_ads or linkedin_ads. Needed only when the profile has more than one ad network and no accountId is given.
accountIdNoThe Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection.
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.
targetingYes
adAccountIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and 'Creates nothing' is largely reinforcement. The description earns credit for disclosing a real return-value behavior with no output schema: 'lower and upper are null when Meta cannot estimate.' It says nothing about latency, rate limits, or account permission requirements for estimates.

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?

Three short sentences, front-loaded with the outcome and followed by the two facts an agent most needs (side-effect-free, null results). No filler and no restatement of the title beyond adding value.

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?

For a tool with a large nested targeting schema, five parameters, and no output schema, the definition is thin: it characterizes the return only by naming lower/upper and their null case, leaving the rest of the response shape and any targeting-validity failure modes unstated. The platform-scope mismatch with the schema is also left unresolved, which could lead an agent to send non-Meta platforms based on this description.

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?

The description references no parameters at all; schema coverage is 60%, so the identity parameters (accountId/profileId/platform) are documented in the schema and the nested targeting object is self-describing but undocumented narratively. There is a real gap: the description scopes the tool to 'Meta' while the schema's platform enum accepts tiktok_ads and linkedin_ads, which the description never reconciles.

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: 'Estimate how many people a Meta targeting spec reaches.' The clause 'Creates nothing' plus the pre-campaign framing makes it unmistakable versus the ads_create_* siblings without needing to name them.

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?

Gives a clear use context — 'before creating a campaign or changing an ad set's targeting' — which tells the agent when to reach for this instead of a create/update call. There is no explicit when-not or named alternative such as ads_list_targeting, so it falls short of a 5.

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.

Resources