mcp-server

remove_marketplace_items

Destructive

MARKETPLACE items: remove — end the chosen items' listings on the LIVE marketplace; a later submit creates a new listing. Use this when the user asks to take specific listings down. 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": "remove_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

A3.9/5.0

Behavior4/5

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

Annotations already flag destructive/openWorld/non-idempotent, but the description adds genuinely new behavioral context: listings are ended on the LIVE marketplace and a subsequent submit creates a fresh listing, which tells the agent the effect is reversible-but-not-idempotent in practice. The confirm gate is also surfaced in the description text. It omits any note on partial failures or per-item error handling.

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?

Front-loads the namespace and action, then delivers purpose, live-marketplace consequence, usage trigger, and the confirm prerequisite in three tight sentences. Density is high with no filler; the only slight cost is that targeting details are packed into a final fragment.

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 destructive mutation with no output schema, the definition covers the essentials an agent needs: what is destroyed, that relisting requires a separate submit, and the confirmation protocol. Minor gaps remain around what happens when item_ids are already unlisted or invalid.

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 80%, so the schema already documents confirm, item_ids, all_items, and marketplace_id. The description restates the item_ids/all_items targeting choice and the confirm requirement without adding format or constraint detail beyond the schema. project_id remains undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('end the chosen items' listings on the LIVE marketplace') and adds the important semantic that removal is reversible via a later submit. An agent can identify the operation immediately, though it does not explicitly distinguish itself from close siblings like remove_all_marketplace_items or clean_marketplace_items.

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 asks to take specific listings down' gives a clear triggering condition, and 'Needs confirm:true after the user agrees' specifies the approval flow. It stops short of naming alternatives (e.g. pause_marketplace_items for temporary takedown), so the selection boundary against siblings is implied rather than 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?