Skip to main content
Glama

ADS Beast

prepare_chatgpt_ads_publish

Prepare uploading a prepared ChatGPT Ads campaign to the platform. Everything is created paused and passes the policy check first; it spends nothing until its ads are approved and a person enables it. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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>",
      "reason": "<reason>"
    },
    "name": "prepare_chatgpt_ads_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
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

A4.3/5.0
Behavior5/5

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

Annotations only cover the safety flags (readOnlyHint=false, destructiveHint=false, openWorldHint=true); the description adds substantive behavior well beyond them — nothing is live, everything is paused, spend is blocked until approval and human enablement, and the tool writes a preview_id with a 15-minute single-use lifetime. The apparent tension between readOnlyHint=false and 'Changes nothing' is resolved by the description itself: it writes a transient preview record rather than changing the campaign.

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?

Three tight sentences, front-loaded with the action and followed by the safety guarantees and the next step; nothing is filler. Minor deduction for the awkward 'Prepare uploading a prepared ... campaign' repetition that slightly obscures the resource name.

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 two-parameter staged-mutation tool with no output schema, the description covers the lifecycle (paused creation, policy check, approval gate, preview TTL, single use, execution handoff) that an agent needs. It does not describe what the preview actually returns or how to recover when the 15-minute preview expires, which are the remaining practical gaps.

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 100% and both parameters are fully documented in-schema (chatgpt_campaign_id sourced from chatgpt_ads_status, reason shown to the approver), so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that baseline, though the mention of preview_id hints at the artifact produced.

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?

States a specific verb and resource — preparing publication of a ChatGPT Ads campaign to the platform — and contrasts it with the executing sibling by saying it only stores a preview_id and that execute_prepared_change follows. An agent can separate it from the many other prepare_* tools because the resource (ChatGPT Ads campaign) and the staged-preview semantics are named outright.

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?

Gives clear context: the campaign is created paused, must pass the policy check, and does not spend until ads are approved and a person enables it, plus the explicit handoff to execute_prepared_change. It stops short of saying when NOT to use it or naming the prerequisite siblings (e.g. chatgpt_ads_draft_generate, chatgpt_ads_policy_check) as required prior steps.

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.