Skip to main content
Glama

List ChatGPT Ads ads

list-openai-ads-ads
Read-only

List the ads in one ChatGPT Ads ad group. Returns a page {data, has_more, last_id}; each ad has id, name, status, review_status and creative. ad_group_id comes from list-openai-ads-ad-groups. get-openai-ads-ad reads one ad; get-openai-ads-ad-insights gives its metrics.

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_group_id": "<ad_group_id>"
    },
    "name": "list-openai-ads-ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNolast_id of the previous page
limitNoPage size
orderNoSort by creation time: desc (newest first) or asc
beforeNofirst_id of the current page
domain_idYesDomain ID from list-domains
ad_group_idYesAd group ID from list-openai-ads-ad-groups

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / ad_group_id / description
      Previous value: -"Parent ad group ID"New value: +"Ad group ID from list-openai-ads-ad-groups"
    • changedInput schema / properties / after / description
      Previous value: -"Cursor for next page"New value: +"last_id of the previous page"
    • changedInput schema / properties / before / description
      Previous value: -"Cursor for prev page"New value: +"first_id of the current page"
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
    • changedInput schema / properties / limit / description
      Previous value: -"Max ads to return"New value: +"Page size"
  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.3/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive safety. The description adds useful behavioral context beyond that: it describes the page envelope {data, has_more, last_id} and the fields on each ad (id, name, status, review_status, creative). It does not mention rate limits or auth, keeping it just below the top score.

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 short sentences, front-loaded with the action and scope, followed by the return shape and sibling routing. No filler.

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?

Complete for a paginated list tool: scope, return value, paging cursor mechanism, and caller-side routing are all covered, and annotations handle the safety profile. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100% and already documents after/before/limit/order and the provenance of domain_id and ad_group_id. The description reinforces the ad_group_id source and how last_id is used for paging, but adds no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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, resource, and scope: 'List the ads in one ChatGPT Ads ad group.' An agent can immediately distinguish it from get-openai-ads-ad (single ad) and list-openai-ads-ad-groups (parent resource) without reading either 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?

The description explicitly routes the agent: ad_group_id comes from list-openai-ads-ad-groups, get-openai-ads-ad reads one ad, get-openai-ads-ad-insights gives metrics. Clear context is provided, though the exclusions are framed as pointers rather than explicit 'do not use this for X' statements.

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