Skip to main content
Glama

Request pausing, resuming or cancelling a campaign

request_campaign_action
Destructive

Ask the user to approve pausing, resuming or cancelling a recurring/evergreen campaign. Cancel is permanent; already-published posts stay on Google. Returns an approval link.

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>",
      "action": "<action>"
    },
    "name": "request_campaign_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
previewNotrue = dry run: nothing is created, run, charged or sent to Google. Returns what would change, the credit cost and whether it would run straight away under Always allow. Use when the user wants to check first.
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / preview
      Added value: +{
      +  "description": "true = dry run: nothing is created, run, charged or sent to Google. Returns what would change, the credit cost and whether it would run straight away under Always allow. Use when the user wants to check first.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, yet the description still adds real substance: cancel is irreversible, published posts remain live on Google, and the call returns an approval link rather than executing immediately. That two-phase approval behavior is not derivable from annotations and materially changes how an agent should sequence the call.

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?

Three tight sentences, front-loaded with the verb and scope, then the destructive consequence, then the return value. No filler or restatement of the title.

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?

No output schema, so stating 'Returns an approval link' fills the return-value gap, and the permanence warning covers the main behavioral risk of a destructive, non-idempotent call. Minor gap: it says nothing about the preview dry-run path or what happens if the user declines, which would matter for an agent deciding whether to fire the request or check first.

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

Parameters5/5

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

Coverage is 33% and the description compensates by explaining what each action means in effect (pause/resume/cancel with cancel being permanent), which is exactly the semantic gap the enum alone leaves open — the enum lists values but not consequences. It does not cover the preview flag, but that parameter already carries a thorough schema description.

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?

Names a specific verb+resource pair ('Ask the user to approve pausing, resuming or cancelling a ... campaign') and enumerates the three actions it covers. It is clearly a human-approval request tool, distinguishable in kind from sibling get_/draft_ tools, though it does not explicitly contrast itself with adjacent request_* siblings.

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?

Implies usage ('Ask the user to approve...') for pausing/resuming/cancelling recurring/evergreen campaigns, and the 'Cancel is permanent' note signals the risk threshold. However, there is no guidance on when to use this vs. a preview flow, and the schema-level dry-run 'preview' parameter is never surfaced in the description.

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