Skip to main content
Glama

Connect a ChatGPT Ads account

connect_chatgpt_ads

Get a link the person opens to connect a client's ChatGPT Ads account (ads shown inside ChatGPT): a short form where they paste that ad account's Advertiser API key and pick the client. One key per ad account. The link lasts 30 minutes and works once. No key is ever entered in the conversation. Use when a ChatGPT Ads tool says nothing is connected, or when asked to connect it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connect_chatgpt_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (openWorldHint=true, idempotentHint=false), the description discloses the operational facts an agent must know: the link lasts 30 minutes, works once, is one key per ad account, and no key is ever entered in the conversation. The single-use/expiry behavior concretely explains the non-idempotent flag and the security constraint.

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?

The purpose is front-loaded in the first clause and each following sentence adds a distinct constraint (one key per account, 30-minute single-use link, no key in chat, when to trigger). Dense but not padded; only the parenthetical 'ads shown inside ChatGPT' is arguably expendable.

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?

With no parameters and no output schema, the description carries the full disclosure burden and meets it: it says what is returned (a link), how it is consumed (short form, key + client pick), how long it lives, and when to call it. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description does extra work by explaining what the human fills in downstream (paste the Advertiser API key, pick the client), which lets the agent set expectations even though no structured parameter exists.

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 description names a specific verb and resource -- 'Get a link the person opens to connect a client's ChatGPT Ads account' -- and immediately scopes it ('ads shown inside ChatGPT'), which separates it from the other connect_* tools in the sibling list. An agent knows exactly what artifact this produces (a link) 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 Guidelines4/5

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

It gives an explicit trigger condition: 'Use when a ChatGPT Ads tool says nothing is connected, or when asked to connect it.' That covers the common entry points. It does not state when NOT to use it or name a specific alternative, which keeps it short of a 5.

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.