Deep Thought Marketing

Pause ads now

pause_ads

Destructive

Pauses a live campaign right away (all of it, or only the channels listed). This is the one change that doesn't wait for review, because it stops spending. Resuming later goes through request_change and the team's review. Call without confirmed first, then with confirmed: true after the person says yes.

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": {
      "order_id": "<order_id>"
    },
    "name": "pause_ads"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Optional reason, passed to the team.
`channels`	No	Optional. Only pause these channels.
`order_id`	Yes	The campaign's order id, from my_campaigns.
`confirmed`	No	Set true only after the person has seen the summary and said yes. Leave out (or false) to get the summary to show them first.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the key non-obvious trait: this is the one change that bypasses review because it stops spending, which explains why the confirmation flow exists. It stops short of saying whether a channel-scoped pause is easily reversible or how long the pause persists, so it is strong but not exhaustive.

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 sentences, front-loaded with the action and scope, then the review-bypass rationale, then the operational call sequence. Every sentence carries information an agent needs to act correctly.

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?

Covers purpose, scope, safety rationale, confirmation workflow, and the alternative tool for resuming; no output schema exists, so return values need not be explained. Minor gap: it does not state what the summary step returns or whether unpaused channels keep spending during a partial pause.

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 order_id, reason, channels, and confirmed are all documented inline, including the confirmed semantics. The description restates the channels behavior ('all of it, or only the channels listed') without adding format or edge-case detail beyond the schema, so the baseline 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?

States a specific verb and resource ('Pauses a live campaign') plus scope ('all of it, or only the channels listed'), and implicitly separates itself from siblings by naming request_change as the path for the inverse operation. An agent can distinguish this from request_change without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit two-step protocol: call without confirmed first to produce a summary, then call with confirmed: true only after the person agrees. It also names the alternative for the opposite operation ('Resuming later goes through request_change'), so when-to-use and when-not-to-use are both covered.

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

All Deep Thought Marketing 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?