Skip to main content
Glama

Pause an ad campaign

pause_ad_campaign

Propose pausing an ad campaign. The change is queued for approval, not applied silently.

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

Input Schema

NameRequiredDescriptionDefault
reasonYes
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds genuinely new context: the change is queued for approval rather than applied silently. That is the single most decision-relevant fact for an agent and it is not derivable from annotations. It omits who approves, latency, and how to check the queued state, so it is not a 5.

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, front-loaded with the action and immediately followed by the non-obvious behavioral caveat. No filler or redundant restatement of the title.

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?

For a two-parameter mutation tool with no output schema, the approval-queue behavior is the key disclosure and it is present. However, with zero schema coverage the definition leaves the required reason parameter and campaign_id sourcing completely unexplained, which is a meaningful gap for correct invocation.

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?

Schema description coverage is 0%, so the description carries the full burden of explaining campaign_id and reason, yet it mentions neither. It does not say where campaign_id comes from, why a reason is mandatory, or that reason is capped at 500 characters. An agent must infer all parameter meaning from names alone.

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 ('Propose pausing an ad campaign'), and the word 'Propose' already signals this is a request rather than a direct mutation. It does not name a sibling tool or explicitly contrast with one, so it stops short of a 5.

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 implied: call this when you want a campaign paused. There is no explicit when-not guidance, no mention of how this differs from adjacent mutation tools like update_ad_budget, and no statement of prerequisites or what to do if a proposal is rejected.

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.

Resources