Skip to main content
Glama

Take Listing Down

cancel_my_listing
Destructive

Takes down one of the caller's own listings on XP -- 'take my listing down', 'I sold them elsewhere'. Buyers can no longer make an offer on it, every open offer on it is rejected, and those buyers are notified that it was removed. A listing with an accepted offer is an agreed sale and cannot be taken down here; XP support handles it. confirm=false returns a preview; confirm=true removes the listing, which cannot be undone. Relisting is a new create_listing. Requires sign-in.

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": {
      "listing_identifier": "<listing_identifier>"
    },
    "name": "cancel_my_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoFalse (default) previews. True takes the listing down.
listing_identifierYesListing identifier from list_my_listings or create_listing.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/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 goes well beyond them: it states the downstream effects (no further offers, all open offers rejected, buyers notified), the hard precondition around accepted offers, and that the action cannot be undone. The addition of the sign-in requirement is also useful context missing from annotations.

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?

Front-loaded with the action and the user phrasings, then effects, then the precondition, then the confirm semantics, then the auth requirement. Every clause carries decision-relevant information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be described, and the definition covers the mutation's consequences and preconditions thoroughly. The remaining gap is minor: it does not say what the preview response contains versus the executed response, which would help an agent chain the two-step flow.

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 100%, so baseline is 3, but the description adds real meaning: confirm=false returns a preview while confirm=true performs an irreversible removal, which tells the agent to preview first. It also documents where listing_identifier comes from (list_my_listings or create_listing), though the schema's own description already covers that.

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?

Names a specific verb and resource ('Takes down one of the caller's own listings'), scopes it to the caller's own listings, and anchors it with the exact user phrasings an agent will encounter ('take my listing down', 'I sold them elsewhere'). It is clearly distinguishable from cancel_my_offer or reject_offer, which act on offers rather than the listing itself.

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 explicit positive conditions, an explicit exclusion (a listing with an accepted offer is an agreed sale and must go through XP support), and the correct alternative for restarting a sale ('Relisting is a new create_listing'). The preview-vs-execute split on confirm is also spelled out, so an agent knows the safe first step.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources