Skip to main content
Glama

get_ad

One ad in full, by its Meta Ad Library id. Use it to read an ad's whole script, see how it is built, or check one ad the user names ('show me the script of ad 862034243491035', 'break down this ad'). Returns the verbatim script sentence by sentence, each labelled Hook, Problem, Agitation, Mechanism, Proof, Product, Offer, CTA…, the ad text and title, format, dates, days live, versions, EU reach history (Meta's total per read day), country and age x gender shares of Meta's breakdown, links to the Ad Library and the shop, and the source of every field. Script sections (hook, problem, CTA…) are served only when every sentence has an English version or the script is in English; otherwise script.sections_status is 'translation_pending' and the transcript comes without section labels (being translated nightly); 'withheld' = this ad's sections can't be served (older breakdown without text). Costs 2 credits.

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": {
      "ad_id": "<ad_id>"
    },
    "name": "get_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYesthe Ad Library id: the digits after ?id= in facebook.com/ads/library/?id=…
formulaNorank formula: v5 and v4 = rank-v4 (default), v3 until 20/11/2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / formula / description
      Previous value: -"rank formula: v4 (default, corrected niches) or v3 (until 20/11/2026)"New value: +"rank formula: v5 and v4 = rank-v4 (default), v3 until 20/11/2026"
    • changedInput schema / properties / formula / enum
      Previous value: -[
      -  "v4",
      -  "v3"
      -]New value: +[
      +  "v5",
      +  "v4",
      +  "v3"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / formula
      Added value: +{
      +  "description": "rank formula: v4 (default, corrected niches) or v3 (until 20/11/2026)",
      +  "enum": [
      +    "v4",
      +    "v3"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full load and does so: it discloses the credit cost (2 credits), the degraded states for script sections ('translation_pending' when not every sentence has an English version, 'withheld' for older ads without text), and the nightly re-translation cadence. Those are exactly the failure modes an agent needs to explain an unexpected 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?

The core purpose and the invocation guidance are front-loaded before the long inventory of returned fields, so the structure serves scanning. The return-field sentence is a dense run-on that could be tightened, but nearly every clause carries distinct information.

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

Completeness5/5

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

There is no output schema, so the description must describe the return payload and it does in detail: verbatim script with section labels, ad text and title, format, dates, days live, versions, EU reach history, demographic shares, links, and per-field provenance. Combined with the documented script-section edge cases, an agent has everything needed to call it and interpret results.

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 coverage is 100%, so the baseline is 3; ad_id's format is already documented in the schema and the description merely restates that it is the Ad Library id. The 'formula' parameter (v5/v4/v3 rank formula) is never mentioned in the description, so no extra meaning is added beyond structured fields.

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?

"One ad in full, by its Meta Ad Library id" gives a specific verb and resource, and the follow-on sentence enumerates concrete uses (read the whole script, inspect structure, check a single named ad). It is clearly a single-ad lookup rather than the brand/aggregate tools in the sibling list, so an agent can select it without opening the 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?

Usage is stated with example utterances ('show me the script of ad 862034243491035', 'break down this ad'), which pins the trigger condition well. What's missing is an explicit exclusion — nothing says to use a search/aggregate sibling when the user has not yet named a specific ad id, so that boundary is left to inference.

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