Skip to main content
Glama

ADS Beast

prepare_campaign_pause

Prepare pausing one campaign. 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": {
      "campaign_id": "<campaign_id>",
      "reason": "<reason>"
    },
    "name": "prepare_campaign_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
campaign_idYesADS Beast id from list_campaigns, not the platform's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing that nothing changes, that a preview_id is stored and returned, and that it has a 15-minute single-use lifetime. This resolves the apparent tension between 'changes nothing' and readOnlyHint=false (a preview record is written). Missing are failure modes, such as what happens on reuse or expiry.

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

Conciseness5/5

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

Two short sentences, zero filler, with the no-side-effect guarantee and the follow-up tool both front-loaded. Every clause earns its place.

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 preparation tool with a fully documented schema and no output schema, this covers the essentials: what is produced (preview_id), how long it lives, and how the flow continues. It could say what the preview actually shows, but nothing needed to call it correctly is absent.

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%, so both campaign_id (internal ADS Beast id, not the platform's) and reason (shown to the approver) are already fully documented. The description adds no syntax or format details beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb and resource ('Prepare pausing one campaign') and immediately distinguishes itself from the sibling that completes the action by naming execute_prepared_change. An agent can tell this apart from prepare_campaign_budget_change or prepare_campaign_enable 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?

The description establishes the two-step workflow clearly: this tool only prepares, then execute_prepared_change performs the action. It does not state when to avoid preparing (e.g., that an unexecuted preview simply expires), but the sequencing guidance is unambiguous enough for correct invocation.

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.