Skip to main content
Glama

Get ChatGPT Ads ad

get-openai-ads-ad
Read-only

Get one ChatGPT Ads ad by id: name, status, review_status, review (with any rejection reason) and creative. ad_id comes from list-openai-ads-ads; its metrics come from get-openai-ads-ad-insights.

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": {
      "domain_id": "<domain_id>",
      "ad_id": "<ad_id>"
    },
    "name": "get-openai-ads-ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYesAd ID from list-openai-ads-ads
domain_idYesDomain ID from list-domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ad_id / description
      Previous value: -"Ad ID"New value: +"Ad ID from list-openai-ads-ads"
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: the exact payload (including the rejection reason in review and the creative) that a single-ID lookup returns. It stops short of covering errors, e.g. what happens for an unknown ad_id.

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?

Two compact sentences, front-loaded with the core action and the returned fields, followed by the provenance/routing note. No filler.

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

Completeness4/5

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

With no output schema, the description compensates by listing the return fields, and annotations cover safety. Only minor gaps remain (error behavior, domain scoping), which is adequate for a simple two-parameter read tool.

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% and the schema already documents both parameters, so the baseline is 3. The description repeats the ad_id provenance already present in the schema and says nothing about domain_id, adding little beyond structured data.

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 ('Get one ChatGPT Ads ad by id') and enumerates the returned fields, which cleanly separates it from list-openai-ads-ads and get-openai-ads-ad-insights.

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 routes the agent: ad_id comes from list-openai-ads-ads and metrics belong to get-openai-ads-ad-insights. It gives clear positive guidance and implicit exclusions, though it doesn't say when not to use this tool (e.g. bulk retrieval).

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