Skip to main content
Glama

Get Ad Details

adsap_get_ad

Read ONE ad in full, live from Meta: its creative content (primary texts, headlines, descriptions, CTA, destination link, URL parameters, image hashes / video ids, Facebook Page and Instagram identity) plus status, timestamps, object_story_id / effective_object_story_id (the underlying post, which carries the ad's likes and comments) and the raw creative specs. Get the ad_id from adsap_list_ads or adsap_get_insights. Use it to inspect an ad's copy and media, to replicate an ad, or to answer 'what does this ad say / link to?' and 'what is switched on?'. SETTINGS: creative_summary.enhancements_on lists the enhancements switched on in the creative, the same list Meta shows in its own tools: key, and name (Meta's name, often the key itself). Use those names as returned, never invent others. Switched on means set to on in the creative; whether one actually runs also depends on the ad's eligibility. creative_summary.standard_enhancements_on is Meta's old bundle switch, which Meta leaves out of its own list: mention it only if the user asks. creative_summary.shop: on means Meta can send people to the business's Facebook or Instagram shop instead of the website (product_set_id = the shop's product set); off means people always go to the website. PARTNERSHIP ADS: creative_summary.partnership gives the partner, the account shown second (partner_page_id, partner_instagram_user_id), and Meta's header choice (both_accounts, first_account_only or meta_picks; null means nothing was set, which Meta shows as both accounts). The account shown first is the ad's own page_id / instagram_user_id. creative_status is Meta's status of the creative: WITH_ISSUES means Meta will not deliver it as it is, IN_PROCESS means Meta is still checking it, so read the ad again in a minute. EARLIER VERSIONS: every edit of an ad's text or media gives it a new creative and keeps the old one. creative_history lists the edits made through Adsap, newest first (when, web app or Claude, previous and new creative id); edits made in Ads Manager are in Meta's change log (adsap_get_account_activities, creative change events carry the old and new creative id). To read an earlier version, pass its id as creative_id: it comes back in older_creative, in the same shape as the current one. Only creatives of the same ad account are read. Read-only: to CHANGE a live ad's creative use adsap_replace_ad_creative.

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_account_id": "<ad_account_id>",
      "ad_id": "<ad_id>"
    },
    "name": "adsap_get_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYesAd ID (numeric). Get it from adsap_list_ads.
creative_idNoOptional. The id of an earlier creative of this ad (from creative_history, or from the creative change events of adsap_get_account_activities) to read that version too. It comes back in older_creative. A creative of another ad account is refused (NOT_FOUND).
ad_account_idYesAd account ID (act_xxx) the ad belongs to. Required. Scopes the request and anchors the Meta budget check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ad_account_id / description
      Previous value: -"Ad account ID (act_xxx) the ad belongs to. Required — scopes the request and anchors the Meta budget check."New value: +"Ad account ID (act_xxx) the ad belongs to. Required. Scopes the request and anchors the Meta budget check."
    • addedInput schema / properties / creative_id
      Added value: +{
      +  "description": "Optional. The id of an earlier creative of this ad (from creative_history, or from the creative change events of adsap_get_account_activities) to read that version too. It comes back in older_creative. A creative of another ad account is refused (NOT_FOUND).",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it declares the tool read-only, explains creative_status values (WITH_ISSUES blocks delivery, IN_PROCESS means re-read in a minute), documents the creative_history/older_creative retrieval path and the cross-account restriction, and points to adsap_get_account_activities for Ads Manager edits. It even warns not to invent enhancement names and to omit standard_enhancements_on unless asked — behavioral context that no structured field provides.

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

Conciseness3/5

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

Purpose is front-loaded and the labeled sections (SETTINGS, PARTNERSHIP ADS, EARLIER VERSIONS) aid scanning, but the prose is dense and long, with field-level explanations of enhancements, shop and partnership semantics that read like documentation of return values. Since no output schema exists those details are defensible, yet several sentences could be tightened without losing agent-relevant meaning.

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 and no annotations, and the description compensates fully: it describes the returned fields, the meaning of status and creative_status values, how earlier creatives surface, and what to do when Meta is still processing. An agent has everything needed to call it and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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; the description goes beyond it by explaining what creative_id actually does (reads an earlier version that returns in older_creative shaped like the current creative, only creatives of the same ad account are readable). ad_account_id and ad_id gain little beyond their schema text, which keeps this at 4 rather than 5.

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?

"Read ONE ad in full, live from Meta" gives a specific verb, resource and scope, and immediately enumerates what comes back (creative texts, headlines, CTA, destination link, image hashes/video ids, page/IG identity, status, object_story_id). It explicitly contrasts itself with adsap_replace_ad_creative for writes and points to adsap_list_ads / adsap_get_insights for obtaining the id, so an agent can distinguish it from siblings without opening any schema.

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

Usage Guidelines5/5

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

It names concrete use cases (inspect copy and media, replicate an ad, answer "what does this ad say / link to" and "what is switched on"), says where to obtain ad_id, and states the exclusion clearly: read-only, use adsap_replace_ad_creative to change a live ad. That is explicit when-to-use plus when-not-to-use with a named alternative.

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