Funkel AI

pause_campaign

Destructive

Pause an active campaign. The campaign engine stops scheduling actions. Two-phase: first call returns a confirmation token + preview; the user reviews an inline card and confirms or cancels; second call (with confirmation_token) commits the pause. Always include campaign_name + app_name so the preview is human-readable. Over MCP: call this tool once, without confirmation_token. It runs right away and returns the result.

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>",
      "campaign_name": "<campaign_name>",
      "app_name": "<app_name>"
    },
    "name": "pause_campaign"
  }
}

Input Schema

Name	Required	Description
`app_name`	Yes	App name (used in the confirm preview)
`campaign_id`	Yes	Campaign id (from a prior list_campaigns) (UUID format, e.g. 550e8400-e29b-41d4-a716-446655440000)
`campaign_name`	Yes	Campaign name (used in the confirm preview)
`confirmation_token`	No	Phase-2 token (omit on phase-1)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: annotations only say destructive/non-idempotent, while the description discloses the side effect (stops scheduling), the confirmation-token two-phase protocol, the inline-card review step, and the special single-call MCP behavior. This is exactly the kind of context annotations cannot carry.

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?

Purpose is front-loaded and each sentence carries information, but the description interleaves the general two-phase flow with the MCP-specific path, which requires the reader to reconcile two modes. Still tight, with no filler.

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

Completeness5/5

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

For a destructive, non-idempotent mutation tool with no output schema, the description covers purpose, side effects, parameter intent, and the exact invocation pattern for the MCP environment. Nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds value by explaining why campaign_name and app_name matter (human-readable preview) and when to supply confirmation_token (phase-2 only, omit over MCP). That meaning is only partially captured by the schema's terse field descriptions.

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 ('Pause an active campaign') and immediately clarifies the operational effect ('the campaign engine stops scheduling actions'), which distinguishes it from siblings like pause_agent and enable_campaign. An agent can identify the tool without opening the 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?

It gives explicit invocation guidance for this context: 'Over MCP: call this tool once, without confirmation_token. It runs right away and returns the result,' and explains the two-phase flow otherwise. It does not name sibling alternatives or exclusions, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Funkel AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?