Skip to main content
Glama

List ChatGPT Ads ad groups

list-openai-ads-ad-groups
Read-only

List the ad groups in one ChatGPT Ads campaign. Returns a page {data, has_more, last_id}; each ad group has id, name, status, bidding_config and serving_issues. campaign_id comes from list-openai-ads-campaigns. get-openai-ads-ad-group reads one; get-openai-ads-ad-group-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>",
      "campaign_id": "<campaign_id>"
    },
    "name": "list-openai-ads-ad-groups"
  }
}

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
campaign_idYesCampaign ID from list-openai-ads-campaigns

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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 / campaign_id / description
      Previous value: -"Parent campaign ID"New value: +"Campaign ID from list-openai-ads-campaigns"
    • 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 ad groups 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.5/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 safety is covered. The description adds real behavioral value beyond that: the paged envelope {data, has_more, last_id} and the per-ad-group field set (id, name, status, bidding_config, serving_issues). It stops short of stating default page size or ordering behavior, which is a minor gap.

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 tight sentences: purpose first, return shape second, routing third. Every clause earns its place with no repetition or 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?

There is no output schema, and the description compensates by describing the page envelope and item fields. Combined with full schema coverage on six parameters and read-only annotations, an agent has everything needed to call this correctly.

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%, so pagination (after/limit/before/order) and the required IDs are fully documented in the schema itself. The description's only addition is reinforcing the campaign_id provenance, which the schema already states. Baseline 3 applies since the schema carries the load.

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 ("List the ad groups") scoped to a single ChatGPT Ads campaign, which immediately distinguishes it from list-openai-ads-campaigns and the single-object get-openai-ads-ad-group. An agent knows exactly what this returns without opening the 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?

Explicitly routes the agent: campaign_id comes from list-openai-ads-campaigns, get-openai-ads-ad-group reads one, get-openai-ads-ad-group-insights gives metrics. That names both the upstream dependency and the two alternatives with the condition that selects each.

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