mcp-server

pause_ad_items

Destructive

AD items: pause — deactivate the chosen items' offers on the LIVE ad channel without deleting them; a later submit resumes them; pause_ad pauses the whole integration. Use this to hold specific listings. Needs confirm:true after the user agrees. Target item_ids or all_items:true.

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": {
      "ad_id": "<ad_id>"
    },
    "name": "pause_ad_items"
  }
}

Input Schema

Name	Required	Description
`ad_id`	Yes	integrationId of the ad (from list_ads).
`confirm`	No	true only after the user approved; without it the call returns confirm_required and nothing runs.
`item_ids`	No	itemId values (from list_ad_items) to act on. Use this OR all_items.
`all_items`	No	Apply to every item of the ad. Use this OR item_ids.
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds context annotations cannot convey: pausing is reversible via a later submit, it affects offers on the LIVE channel rather than deleting items, and omitting confirm:true yields confirm_required and runs nothing. That is exactly the behavioral detail an agent needs before invoking a mutation.

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?

One compact sentence-pair; the primary action is front-loaded and the sibling contrast and confirm requirement follow in priority order. Slightly telegraphic with semicolons, but no filler.

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 5-parameter mutation with no output schema, the description covers reversibility, channel scope, the confirm gate, and its confirm_required failure mode. Only the project_id parameter and any rate/ownership constraints go unaddressed.

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 80%, so baseline is 3; the description still adds value by stating the ad_id + (item_ids XOR all_items) targeting model and tying confirm:true to user approval. It doesn't explain project_id, but that gap is minor at this coverage level.

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?

"AD items: pause — deactivate the chosen items' offers on the LIVE ad channel without deleting them" gives a specific verb, resource, scope (LIVE channel) and explicitly contrasts with pause_ad (whole integration). An agent can differentiate it from pause_ad, submit_ad_items, and clean_ad_items 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 Guidelines5/5

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

Names the alternative ("pause_ad pauses the whole integration") and the intended use case ("Use this to hold specific listings"), plus the precondition ("Needs confirm:true after the user agrees"). When-to-use, when-not, and prerequisite are all stated.

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

All mcp-server 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?