Skip to main content
Glama

ChatGPT Ads: spend, clicks and conversions

chatgpt_ads_report
Read-onlyIdempotent

ChatGPT Ads performance for one client: spend, impressions, clicks, CTR, CPC, goal conversions and cost per conversion, by campaign (default), ad group or ad, plus totals. Money is in the account currency. Dates are the account's own time zone; the default is the last 30 full days.

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": {
      "account": "<account>"
    },
    "name": "chatgpt_ads_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLast N full days, ending yesterday
levelNocampaign
sinceNoYYYY-MM-DD; with until, overrides days
untilNoYYYY-MM-DD, inclusive
accountYesThe ChatGPT Ads account: its client's name, the account name, or its adacct_ id (chatgpt_ads_list_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful interpretation context — money in account currency, dates in account time zone, default of the last 30 full days — but says nothing about result size, limits, or what the response looks like (no output schema exists).

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, front-loaded with the resource and metrics, followed by unit and time-zone caveats. Every clause carries information an agent would otherwise have to guess.

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?

For a five-parameter read-only reporting tool with no output schema, the description lists the returned metrics and the currency/time-zone semantics, which is what an agent needs to interpret results. Missing only response shape/size and any explicit alternative-tool routing.

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 80%, so the schema already documents days, level, since/until and the account resolution with a pointer to chatgpt_ads_list_accounts. The description only reinforces defaults and adds the detail that totals are included alongside breakdowns, which is a small increment over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific resource and metric set (spend, impressions, clicks, CTR, CPC, conversions, cost per conversion) for one account, and names the breakdown levels. It is unmistakably a reporting tool, though it never says how it differs from nearby siblings such as chatgpt_ads_leads or chatgpt_ads_list_campaigns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'performance for one client' plus the default 30-full-day window tells the agent the typical call, but there is no explicit when-to-use or when-to-prefer-another-tool guidance. Nothing routes the agent between this and the other reporting tools.

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.