Skip to main content
Glama

Visibility Genies

Read ChatGPT Ads performance

get_chatgpt_ads_performance
Read-only

The connected ChatGPT Ads account's spend, impressions, clicks, CTR, CPC, conversions, cost per conversion, attributed sales and ROAS for a date range, in total and per campaign, most spend first, from what the daily pull stored. Conversions and sales counted within 30 days of a click or 1 day of a view, as ChatGPT Ads Manager counts them by default. Money is in the account's currency (currencyCode). Days are in the account's time zone; at most 90 days. ChatGPT Ads shares no prompts or topics. Read-only; uses no credits.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_chatgpt_ads_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateNoLast day (YYYY-MM-DD). Use with startDate. Without both, the last 30 stored days. At most 90 days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoFirst day (YYYY-MM-DD, the ad account's time zone). Use with endDate.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
reasonNo
totalsNo
endDateNo
messageNo
failedAtNo
campaignsNo
startDateNo
connectUrlNo
keyRefusedNo
accountNameNo
currencyCodeNo
storedThroughNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/destructive/openWorld annotations, it discloses substantive behavior: results reflect what the daily pull stored (freshness), conversions and sales use a 30-day click / 1-day view attribution window matching Ads Manager defaults, money is in currencyCode, days follow the account time zone, and the call consumes no credits. These are exactly the facts an agent needs and none of them are derivable from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the metric/grouping summary, then freshness, attribution, currency, time zone, and limits — a logical order with no filler. It loses a point for mild redundancy with the schema, repeating the 90-day cap and date-range defaults that are already in the parameter descriptions.

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?

For a read-only reporting tool with an output schema already defining the return shape, the description covers everything else that matters: data source freshness, attribution model, currency, time zone, range limit, and cost model. No material gap remains for an agent to call it 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%, and the schema itself already documents the YYYY-MM-DD format, the 30-day default, the 90-day cap, and that projectId is required and billed. The description largely restates those facts; its only marginal additions are the time-zone framing for startDate and the result ordering. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The opening sentence states a specific verb (read) and resource (ChatGPT Ads performance) and enumerates the exact metrics returned (spend, impressions, clicks, CTR, CPC, conversions, cost per conversion, attributed sales, ROAS) plus grouping (total and per campaign) and ordering (most spend first). That is enough to distinguish it from the sibling platform-performance tools like get_meta_ads_performance and get_tiktok_ads_performance without opening a 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?

It gives clear context for use: a date range bounded at 90 days, a default of the last 30 stored days when dates are omitted, and a note that ChatGPT Ads shares no prompts or topics, which implicitly steers a prompts/topics question elsewhere. It stops short of explicitly naming an alternative tool or stating when not to use it.

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