Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

add_to_wantlist

Add music releases to your Discogs wantlist by specifying username and release ID. Track desired vinyl, CDs, or cassettes for future purchase.

Instructions

Add a release to a user's wantlist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
release_idYes
notesNo
ratingNo

Implementation Reference

  • Tool handler implementation: defines the 'add_to_wantlist' tool with execute function that instantiates UserService and calls wants.addItem(args) to add the release to the wantlist.
    export const addToWantlistTool: Tool<FastMCPSessionAuth, typeof UserWantlistItemParamsSchema> = {
      name: 'add_to_wantlist',
      description: `Add a release to a user's wantlist`,
      parameters: UserWantlistItemParamsSchema,
      execute: async (args) => {
        try {
          const userService = new UserService();
          const wantlistItem = await userService.wants.addItem(args);
    
          return JSON.stringify(wantlistItem);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod schema defining input parameters for add_to_wantlist: merges username input with release ID and optional notes/rating.
    /**
     * Schema for adding or editing a release in a user's wantlist
     */
    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 addToWantlistTool (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 tools registration, ensuring the tool is registered on the server.
    registerUserWantlistTools(server);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Add' implies a write/mutation operation, but the description doesn't address permissions needed, whether this creates or updates existing entries, what happens on duplicate attempts, rate limits, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 that gets straight to the point with no wasted words. It's appropriately sized for the basic operation described and front-loads the core action and target.

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 mutation tool with 4 parameters (2 required), 0% schema coverage, no annotations, and no output schema, this description is insufficient. It doesn't address behavioral aspects, parameter meanings, usage context, or what to expect from the operation. The description fails to compensate for the lack of structured documentation.

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?

With 0% schema description coverage for all 4 parameters, the description provides no information about what 'username', 'release_id', 'notes', or 'rating' mean or how they should be used. The description mentions adding a release but doesn't explain the relationship between these parameters, leaving the agent to guess about their purpose and proper usage.

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 ('Add') and resource ('a release to a user's wantlist'), making the purpose immediately understandable. However, it doesn't differentiate from similar sibling tools like 'add_release_to_user_collection_folder' or 'edit_item_in_wantlist', which would require more specificity about what distinguishes this particular wantlist operation.

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. With multiple sibling tools for managing collections, wantlists, and ratings, there's no indication of prerequisites, when this is appropriate versus 'edit_item_in_wantlist' or 'rate_release_in_user_collection', or any constraints on usage.

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