Skip to main content
Glama

Get ChatGPT Ads ad group

get-openai-ads-ad-group
Read-only

Get one ChatGPT Ads ad group by id: name, status, bidding_config and context_hints, without serving_issues (list-openai-ads-ad-groups has those). ad_group_id comes from list-openai-ads-ad-groups; its ads come from list-openai-ads-ads and its metrics from get-openai-ads-ad-group-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_group_id": "<ad_group_id>"
    },
    "name": "get-openai-ads-ad-group"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed2 schema fields changed
    • changedInput schema / properties / ad_group_id / description
      Previous value: -"Ad group ID"New value: +"Ad group ID from list-openai-ads-ad-groups"
    • 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.4/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 valuable scope detail by naming the returned fields and explicitly flagging that serving_issues is excluded. It does not cover failure behavior (e.g. what happens for an unknown or cross-domain ad_group_id), which is the only remaining 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?

A single dense sentence with the primary action front-loaded and secondary routing facts in parentheses. Every clause (returned fields, excluded field, id source, related tools) carries information an agent needs; nothing is 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 returned fields and the deliberately excluded one, plus pointers to sibling tools for the surrounding resources. Only error/not-found semantics and any permission or domain-scoping constraints are left unaddressed.

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 both parameters already carry provenance descriptions ('Domain ID from list-domains', 'Ad group ID from list-openai-ads-ad-groups'). The description repeats the ad_group_id provenance and omits domain_id entirely, adding little beyond the schema, so the baseline 3 applies.

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 group by id') and enumerates exactly which fields are returned (name, status, bidding_config, context_hints), then names the field it omits. An agent can distinguish it from list-openai-ads-ad-groups and get-openai-ads-ad-group-insights without opening any 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: the id comes from list-openai-ads-ad-groups, ads come from list-openai-ads-ads, metrics come from get-openai-ads-ad-group-insights, and serving_issues should be fetched via the list tool instead. Both when-to-use and when-not-to-use are stated with named alternatives.

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