Skip to main content
Glama

ADS Beast

chatgpt_ads_status

Read-only

Connected ChatGPT Ads accounts, campaigns, ad review statuses and what blocks delivery.

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": "chatgpt_ads_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that it surfaces what blocks delivery, which is genuinely useful output context given there is no output schema. It does not say whether it hits live ad-platform APIs or how much data is returned.

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

Conciseness3/5

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

One short sentence with no padding, so nothing is wasted, but it is under-specified rather than economical. The most actionable information (what blocks delivery) is present but not front-loaded with a clear action verb.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with an undocumented optional parameter and no output schema, the description should explain what client_id does and roughly what the response contains. It gives a partial picture of returned data but leaves the parameter entirely unexplained.

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

Parameters2/5

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

There is one parameter, client_id, with 0% schema description coverage, and the description never mentions it. The agent cannot tell whether client_id scopes results to a single connected account or is optional and defaults to all accounts.

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

Purpose3/5

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

The description lists the resources it reports on (accounts, campaigns, ad review statuses, delivery blockers), which conveys the domain, but it is a noun fragment with no verb, so the agent must infer that this is a read/status retrieval tool. It is distinguishable from chatgpt_ads_policy_check and chatgpt_ads_review_sync only by inference, not by explicit contrast.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any alternative such as policy_check or review_sync. The agent is left to guess whether this is a diagnostic entry point or a follow-up to another 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.