Skip to main content
Glama

ADS Beast

chatgpt_ads_review_sync

Asks ChatGPT Ads for the review status of a campaign's ads and stores it in ADS Beast. Nothing is enabled: a campaign with no approved ad must stay off.

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": {
      "chatgpt_campaign_id": "<chatgpt_campaign_id>"
    },
    "name": "chatgpt_ads_review_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatgpt_campaign_idYesADS Beast id of the ChatGPT Ads campaign, from chatgpt_ads_status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true; the description adds genuine context beyond them by disclosing that data is persisted into ADS Beast and that the operation is a gating step, not an enablement ('Nothing is enabled: a campaign with no approved ad must stay off'). It does not cover behavior on external API failure, whether stored status is overwritten, or rate limits.

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?

Two short front-loaded sentences with no filler. The second sentence is slightly cryptic ('Nothing is enabled' does not clearly say what is being kept off), costing a little precision.

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

Completeness3/5

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

Adequate for a one-parameter tool with full schema coverage and no output schema, but a sync operation that writes to an external system leaves the agent without any sense of what comes back (per-ad statuses, counts, failures) or how partial failures are reported.

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?

Only one parameter at 100% schema coverage, and the schema already explains it is the ADS Beast id sourced from chatgpt_ads_status. The description only alludes to 'a campaign's ads' and adds no new meaning about the id's provenance or validity.

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?

States a specific verb and resource ('asks ChatGPT Ads for the review status of a campaign's ads') plus the side effect ('stores it in ADS Beast'). It is distinguishable from chatgpt_ads_status because it explicitly adds the persist step, though it never names that sibling as the alternative for read-only status checks.

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 only implied: refresh/sync review status before enabling anything. There is no explicit 'use when' clause, no when-not condition, and no named alternative (such as chatgpt_ads_status for a read-only status read) despite close siblings existing.

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.