Ads · MCP TOOL
get_ad_detail
Read one stored creative and its delivery context.
When to use it
Inspect copy, advertiser, linked apps and media. Unknown creatives and creatives without displayable media are reported as not found.
Parameters
Defaults and constraints come from the published Zod input schema. “—” means no schema default or no enum restriction. Use JSON values of the listed type; additional handler rules are described above.
Example prompts
- Read the stored creative with Meta ID 123456789.
Example call
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_ad_detail",
"arguments": {
"adId": "meta:123456789"
}
}
}Example result
Illustrative, abridged JSON-RPC result. Only selected fields are shown; empty arrays illustrate a response with no rows. These are not current catalog observations. Parse the JSON inside content[].text.
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"content": [
{
"type": "text",
"text": "{\"id\":\"meta:123456789\",\"network\":\"meta\"}"
}
]
}
}Free vs paid results
The explicitly requested creative keeps its identity on Free. Linked app revenue figures are hidden; Basic and Pro unlock them.
Paid access does not fill coverage gaps or unknown values. Returned plan metadata and lock notes explain redaction where applicable. Read the full Free data policy.
Rate limits and usage credit
Days reset at 00:00 UTC. The combined ISO week resets Monday at 00:00 UTC. Every served tool call counts, including cached reads. Failed or refused calls are released along with any charge. Compare plans.
After either allowance, Basic and Pro can opt in to pay $0.02 in usage credit per call to get_ad_detail. A call exceeding both windows is charged once. Free is refused past its allowances; paid plans without opt-in or enough credit are also refused with HTTP 402 / JSON-RPC -32004.
Credential request throttles and, for live keyword work, store-work throttles also apply. Follow retry instructions in the error reference.