mcp-server

pause_ad

Idempotent

Pause an ad — synchronization to the channel stops until it is resumed with resume_ad. Use this when the user wants an ad to stop syncing. Ads are product-listing channels (Google Shopping, Meta catalog, Microsoft, price comparison) for the merchant's physical products, not marketplaces: they publish products to the channel and have no order sync. Returns {integrationId, action:'pause', status:'paused', kind:'ads'}. ad_id is from list_ads. project_id is OPTIONAL (inferred for a single-project customer; project_id_required otherwise — then call list_projects).

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

Input Schema

Name	Required	Description	Default
`ad_id`	Yes
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavior: the pause is reversible only via resume_ad, and the exact response shape ({integrationId, action:'pause', status:'paused', kind:'ads'}) is disclosed. It does not cover permission requirements or what happens to already-published channel items.

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?

It is front-loaded with the action and effect, then the disambiguation, then parameters, which is the right order. The ad-vs-marketplace sentence is long but does real routing work; without it the definition would be materially weaker, so little is wasted.

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 two-parameter mutation with no output schema and no annotations-level detail, the description covers effect, reversibility, return shape, id provenance and the project_id fallback. Nothing an agent needs to call it correctly is missing.

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?

Schema description coverage is 0%, so the description must carry parameter meaning and it does: ad_id provenance is given ("from list_ads") and the optionality/fallback logic for project_id is spelled out, including the project_id_required error path that requires calling list_projects. This is the strongest area of the definition.

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?

The description opens with a specific verb+resource ("Pause an ad") and immediately defines the effect ("synchronization to the channel stops"). It then explicitly defines what an ad is versus a marketplace, which separates it from pause_marketplace and pause_marketplace_items 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 Guidelines4/5

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

"Use this when the user wants an ad to stop syncing" gives an explicit use condition, and it names resume_ad as the counterpart action. The ad-vs-marketplace definition implicitly steers away from pause_marketplace, though it never states that exclusion outright nor mentions pause_feed/pause_ad_items as alternatives.

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?