Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

delete_item_in_wantlist

Remove a music release from a Discogs user's wantlist by specifying the username and release ID.

Instructions

Delete a release from a user's wantlist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
release_idYes
notesNo
ratingNo

Implementation Reference

  • MCP tool object for 'delete_item_in_wantlist' including the handler execute function that delegates to UserService.wants.deleteItem
    export const deleteItemInWantlistTool: Tool<
      FastMCPSessionAuth,
      typeof UserWantlistItemParamsSchema
    > = {
      name: 'delete_item_in_wantlist',
      description: `Delete a release from a user's wantlist`,
      parameters: UserWantlistItemParamsSchema,
      execute: async (args) => {
        try {
          const userService = new UserService();
          await userService.wants.deleteItem(args);
    
          return 'Release deleted from wantlist';
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod schema defining input parameters for the tool: username, release_id, optional notes and rating
    export const UserWantlistItemParamsSchema = UsernameInputSchema.merge(
      ReleaseIdParamSchema.extend({
        notes: z.string().optional(),
        rating: z.number().int().min(0).max(5).optional(),
      }),
    );
  • Registration function that adds the delete_item_in_wantlist tool (and related wantlist tools) to the FastMCP server
    export function registerUserWantlistTools(server: FastMCP): void {
      server.addTool(getUserWantlistTool);
      server.addTool(addToWantlistTool);
      server.addTool(editItemInWantlistTool);
      server.addTool(deleteItemInWantlistTool);
    }
  • Invocation of registerUserWantlistTools in the main registerTools function, which registers all tools including delete_item_in_wantlist
    registerUserWantlistTools(server);
  • UserWantsService.deleteItem method that performs the actual Discogs API DELETE request to remove the release from the wantlist
    async deleteItem({ username, release_id }: UserWantlistItemParams): Promise<void> {
      try {
        await this.request(`/${username}/wants/${release_id}`, {
          method: 'DELETE',
        });
      } catch (error) {
        // If it's already a Discogs error, just rethrow it
        if (isDiscogsError(error)) {
          throw error;
        }
    
        // For other unexpected errors, wrap them
        throw new Error(`Failed to delete from wantlist: ${String(error)}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is 'Delete,' implying a destructive mutation, but doesn't clarify if this is permanent, reversible, requires specific permissions, or has side effects (e.g., affecting ratings or notes). This leaves significant gaps for a tool that modifies user data.

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, direct sentence with zero wasted words, making it easy to parse. It's front-loaded with the core action and resource, though this brevity contributes to gaps in other dimensions.

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 tool with 4 parameters (2 required), 0% schema coverage, no annotations, and no output schema, the description is inadequate. It lacks details on behavior, parameter meanings, error conditions, or return values, leaving the agent with insufficient context to use it safely and effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate by explaining parameters, but it adds no information beyond what's inferred from the tool name. It doesn't clarify the purpose of 'username' (e.g., target user), 'release_id' (e.g., identifier for the music release), or optional parameters like 'notes' and 'rating' (e.g., whether they're ignored or have side effects).

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 action ('Delete') and the resource ('a release from a user's wantlist'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'delete_release_from_user_collection_folder' or 'edit_item_in_wantlist', but the specificity of 'wantlist' provides some implicit distinction.

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., the item must exist in the wantlist), compare it to similar tools like 'edit_item_in_wantlist' for modifications, or indicate when deletion is appropriate versus other operations.

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