mcp-server

pause_marketplace_items

Destructive

MARKETPLACE items: pause — deactivate the chosen items' offers on the LIVE marketplace without deleting them; a later submit resumes them; pause_marketplace 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": {
      "marketplace_id": "<marketplace_id>"
    },
    "name": "pause_marketplace_items"
  }
}

Input Schema

Name	Required	Description
`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_marketplace_items) to act on. Use this OR all_items.
`all_items`	No	Apply to every item of the marketplace. Use this OR item_ids.
`project_id`	No
`marketplace_id`	Yes	integrationId of the marketplace (from list_marketplaces).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds real value beyond the annotations: offers are deactivated, not deleted, and a later submit resumes them, plus the confirm gate returns confirm_required with nothing executed. The only mild tension is that annotations carry destructiveHint=true while the prose stresses reversibility; it is a state-changing, open-world operation, so this is not a hard contradiction but the description could reconcile the two more explicitly.

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?

The scope and the sibling differentiator lead the text, and every sentence carries information. The semicolon-chained phrasing is dense but readable; a touch of fragmentation keeps it from a 5.

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 the effect, reversibility, the confirm guard, and the confirm_required response. What is missing is only minor: the undocumented project_id and whether the pause is applied asynchronously.

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 already 80%, yet the description still adds the either/or rule for item_ids vs all_items and the semantics of confirm (only after user approval). It does not explain project_id, whose schema entry has no description, so a small residual gap remains.

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 precise verb and resource ('pause — deactivate the chosen items' offers on the LIVE marketplace') and explicitly contrasts with the sibling pause_marketplace, which pauses the whole integration. An agent can pick between them 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 the when ('Use this to hold specific listings'), the alternative and its distinguishing condition (pause_marketplace = whole integration), and the naming convention that selects it (item_ids vs all_items:true). It also flags the confirm:true prerequisite, which is the main misuse risk.

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?