delete_marketplace_listing
Remove a marketplace listing from your Discogs inventory by providing its listing ID.
Instructions
Delete a marketplace listing
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listing_id | Yes |
Remove a marketplace listing from your Discogs inventory by providing its listing ID.
Delete a marketplace listing
| Name | Required | Description | Default |
|---|---|---|---|
| listing_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must fully convey behavioral traits. It only repeats the action without disclosing any side effects (e.g., permanence, required permissions, impact on orders or users). This is a minimal description that fails to inform an agent about important behaviors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (4 words) and contains no unnecessary words, but it lacks structure and substance. It is minimally concise but fails to earn its place by providing any helpful context or details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema, no annotations), the description should explain the parameter and behavioral effects. It does neither, leaving the agent with no useful information beyond the tool name. This is completely inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description does not mention the 'listing_id' parameter or its meaning. The agent must infer that this ID identifies the listing to delete, but the description provides no clarity. For a single required parameter, this is a significant oversight.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states 'Delete a marketplace listing', which clearly indicates the action and resource. However, it is essentially a tautology of the tool name (delete_marketplace_listing) and does not differentiate how this deletion is unique compared to sibling tools like create or update. It provides no additional context about what 'marketplace listing' means.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives (e.g., edit_marketplace_listing or get_marketplace_listing). There is no indication of prerequisites, consequences, or context for deletion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cswkim/discogs-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server