Skip to main content
Glama

Get ChatGPT Ads campaign

get-openai-ads-campaign
Read-only

Get one ChatGPT Ads campaign by id: name, status, budget, schedule and targeting, without serving_issues (list-openai-ads-campaigns has those). campaign_id comes from list-openai-ads-campaigns; its metrics come from get-openai-ads-campaign-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>",
      "campaign_id": "<campaign_id>"
    },
    "name": "get-openai-ads-campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_idYesDomain ID from list-domains
campaign_idYesCampaign ID from list-openai-ads-campaigns

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / campaign_id / description
      Previous value: -"OpenAI Ads 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"
  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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value by disclosing the exact field set returned and one field deliberately omitted, which matters because there is no output schema. It stops short of noting error behavior for an unknown campaign_id or any auth requirement.

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 tight sentences with no filler; the returned-field list comes first and the sibling routing follows. Every clause carries information an agent would otherwise have to infer.

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's field enumeration is what tells the agent what comes back, and the cross-references cover the surrounding tool graph. It is nearly complete, missing only behavior on a missing or nonexistent campaign_id.

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 carry their own descriptions, so the schema does the heavy lifting. The description corroborates campaign_id's provenance from list-openai-ads-campaigns but says nothing about domain_id, adding little beyond the structured fields.

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 campaign by id') and enumerates the returned fields (name, status, budget, schedule, targeting). It explicitly excludes serving_issues and names the sibling that has them, so the boundary with list-openai-ads-campaigns is unambiguous.

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?

Names both alternatives and the conditions that select them: list-openai-ads-campaigns for serving_issues, get-openai-ads-campaign-insights for metrics. It also states where campaign_id originates, giving the agent the full call sequence rather than just the call.

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