Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

get_user_wantlist

Retrieve a user's Discogs wantlist to view desired music releases, with options to sort by date, artist, title, or other criteria.

Instructions

Returns the list of releases in a user's wantlist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
pageNo
per_pageNo
sortNo
sort_orderNo

Implementation Reference

  • The execute handler for the 'get_user_wantlist' MCP tool. Instantiates UserService and delegates to its wants.getList method to fetch and return the user's wantlist as JSON.
    execute: async (args) => {
      try {
        const userService = new UserService();
        const wantlist = await userService.wants.getList(args);
    
        return JSON.stringify(wantlist);
      } catch (error) {
        throw formatDiscogsError(error);
      }
    },
  • Zod schema defining the input parameters for the get_user_wantlist tool, merging username input with query params for filtering/sorting the wantlist.
    export const UserWantlistParamsSchema = UsernameInputSchema.merge(
      QueryParamsSchema(['added', 'artist', 'label', 'rating', 'title', 'year'] as const),
    );
  • Core implementation in UserWantsService.getList: makes authenticated API request to Discogs /${username}/wants endpoint, validates response with Zod, handles errors.
    async getList({ username, ...options }: UserWantlistParams): Promise<UserWantlist> {
      try {
        const response = await this.request<UserWantlist>(`/${username}/wants`, {
          params: options,
        });
    
        // Validate the response using Zod schema
        const validatedResponse = UserWantlistSchema.parse(response);
        return validatedResponse;
      } catch (error) {
        // If it's already a Discogs error, just rethrow it
        if (isDiscogsError(error)) {
          throw error;
        }
    
        // For validation errors or other unexpected errors, wrap them
        throw new Error(`Failed to get wantlist: ${String(error)}`);
      }
    }
  • Registration function that adds the get_user_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 the wantlist tools registration within the central registerTools function.
    registerUserWantlistTools(server);
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 this is a read operation ('Returns'), but doesn't mention authentication requirements, rate limits, pagination behavior (implied by 'page' and 'per_page' parameters but not explained), error conditions, or what the return format looks like. This leaves significant gaps for an agent to understand how to use the tool effectively.

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 a simple retrieval tool and front-loads the core functionality.

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?

Given the tool's moderate complexity (5 parameters, pagination, sorting), no annotations, and no output schema, the description is insufficient. It doesn't explain the return format, authentication needs, error handling, or parameter semantics. For a tool that retrieves user-specific data with multiple configuration options, this leaves too many unknowns for effective use.

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 and 5 parameters, the description provides no information about any parameters. It doesn't explain what 'username' refers to (Discogs username?), what 'sort' options mean, or how pagination works. The description fails to compensate for the complete lack of parameter documentation in the schema.

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 ('Returns') and resource ('list of releases in a user's wantlist'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'get_user_inventory' or 'get_user_collection_items', which also retrieve user-specific lists of releases.

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. There are multiple sibling tools for retrieving user data (e.g., 'get_user_inventory', 'get_user_collection_items'), but the description doesn't explain when a wantlist is appropriate versus other collections or how this tool relates to 'edit_item_in_wantlist' and 'delete_item_in_wantlist'.

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