Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

delete_marketplace_listing

Remove a marketplace listing from Discogs by specifying its listing ID. This tool helps users manage their Discogs music catalog by deleting unwanted listings.

Instructions

Delete a marketplace listing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listing_idYes

Implementation Reference

  • The main handler implementation for the 'delete_marketplace_listing' tool. It creates a MarketplaceService instance and calls deleteListing(args) to perform the deletion, returning a success message or formatted error.
    export const deleteMarketplaceListingTool: Tool<FastMCPSessionAuth, typeof ListingIdParamSchema> = {
      name: 'delete_marketplace_listing',
      description: 'Delete a marketplace listing',
      parameters: ListingIdParamSchema,
      execute: async (args) => {
        try {
          const marketplaceService = new MarketplaceService();
          await marketplaceService.deleteListing(args);
    
          return 'Listing deleted successfully';
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod schema defining the input parameters for the tool: an object with 'listing_id' as a positive integer.
    export const ListingIdParamSchema = z.object({
      listing_id: z.number().int(),
    });
  • Registers the deleteMarketplaceListingTool with the FastMCP server instance inside the registerMarketplaceTools function.
    server.addTool(deleteMarketplaceListingTool);
  • Calls registerMarketplaceTools as part of the overall tools registration in tools/index.ts.
    registerMarketplaceTools(server);
  • src/index.ts:32-32 (registration)
    Top-level registration call that includes marketplace tools via registerTools.
    registerTools(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete' implies a destructive, irreversible mutation, but the description doesn't state permission requirements, whether deletion is permanent, what happens to associated data, or error conditions. For a destructive tool with zero annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place.

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

Completeness2/5

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

For a destructive mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't address critical context like permissions, consequences, error handling, or return values. The agent lacks sufficient information to use this tool safely and effectively.

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?

The description doesn't mention parameters at all, but schema description coverage is 0% (the single parameter 'listing_id' has no description in the schema). The description doesn't compensate by explaining what 'listing_id' represents or its format. However, with only one parameter, the baseline is higher than for multi-parameter tools with poor coverage.

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?

The description clearly states the verb ('Delete') and resource ('a marketplace listing'), making the tool's purpose immediately understandable. It distinguishes from sibling tools like 'update_marketplace_listing' and 'get_marketplace_listing' by specifying the destructive action. However, it doesn't specify scope or constraints beyond the basic action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing listing), exclusions, or relationships with sibling tools like 'update_marketplace_listing' or 'create_marketplace_listing'. The agent must infer usage from the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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