Skip to main content
Glama
shinypebble

openai-ads-mcp

by shinypebble

get_ad

Read-only

Retrieve an ad by ID and diagnose non-serving issues, including parent campaign status and effective serving problems.

Instructions

Fetch one ad by id — use to diagnose non-serving ads.

Backfills the parent ad_group_id and the effective serving_issues (the API's own undocumented codes plus parent-not-active derived from the tree), since a paused parent campaign/ad group leaves an ad active but not serving. Both require one walk of the account tree; an archived ad is absent from that walk, so its parents stay blank.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
ad_group_idNo
nameNo
statusNo
creativeNo
review_statusNo
reviewNo
serving_issuesNo
image_urlNo
created_atNo
updated_atNo
Behavior5/5

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

Adds significant behavioral context beyond readOnlyHint annotation: explains backfilling of ad_group_id and serving_issues, the tree walk, and behavior for archived ads. No contradiction with annotations.

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 sentences with no wasted words. First sentence provides a clear summary, following sentences add necessary behavioral details without redundancy.

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?

The description covers purpose, usage, behavioral details, and limitations. The presence of an output schema means return values need not be explained. Complete for a single-ad fetch tool.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description only minimally references the parameter as 'by id' without adding format or constraints. Given the low coverage, more detail would be expected.

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?

The description clearly states the verb 'Fetch' and resource 'one ad by id', and specifies the use case 'diagnose non-serving ads'. This distinguishes it from sibling tools like get_ad_group or ad_performance.

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?

Explicitly states when to use: 'use to diagnose non-serving ads'. Provides context about backfill behavior and limitations for archived ads, but does not explicitly name alternatives or when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shinypebble/openai-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server