delete_marketplace_listing
Remove a marketplace listing on Discogs by specifying the listing ID to delete.
Instructions
Delete a marketplace listing
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listing_id | Yes |
Remove a marketplace listing on Discogs by specifying the listing ID to delete.
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 are provided, and the description fails to disclose critical behavioral traits such as whether deletion is permanent, requires authorization, or has any side effects. For a destructive action, this is a significant omission.
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 a single sentence, which is concise but lacks necessary detail. While it is short, it does not provide enough information to be fully useful, so it does not earn a higher score.
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 no annotations and no output schema, the description leaves out essential context about the tool's effect, requirements, and return value. For a delete operation, this is incomplete and risks misuse.
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?
With 0% schema description coverage, the description does not explain the only parameter (listing_id) beyond its name. The agent must guess its meaning and format, which is insufficient for correct invocation.
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?
The description clearly states the action ('delete') and the resource ('marketplace listing'), which distinguishes it from sibling tools like create_marketplace_listing and update_marketplace_listing. However, it lacks additional context such as permanence or irreversibility that would make it a 5.
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 on when to use this tool versus alternatives, nor any prerequisites or conditions. The description simply says 'Delete a marketplace listing', leaving the agent to infer appropriate usage without explicit direction.
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