Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

get_user_collection_folders

Retrieve a list of folders from a user's Discogs music collection to organize and manage catalog items.

Instructions

Retrieve a list of folders in a user's collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes

Implementation Reference

  • The main handler implementation for the 'get_user_collection_folders' MCP tool. Defines the tool object with name, description, input schema, and the execute function that fetches collection folders via UserService.
    export const getUserCollectionFoldersTool: Tool<FastMCPSessionAuth, typeof UsernameInputSchema> = {
      name: 'get_user_collection_folders',
      description: `Retrieve a list of folders in a user's collection`,
      parameters: UsernameInputSchema,
      execute: async (args) => {
        try {
          const userService = new UserService();
          const collectionFolders = await userService.collection.getFolders(args);
    
          return JSON.stringify(collectionFolders);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod input schema used by the tool, requiring a non-empty 'username' string.
    export const UsernameInputSchema = z.object({
      username: z.string().min(1, 'username is required'),
    });
  • Direct registration of the tool with the FastMCP server instance.
    server.addTool(getUserCollectionFoldersTool);
  • Top-level registration call that includes the user collection tools, encompassing 'get_user_collection_folders'.
    registerUserCollectionTools(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 but offers minimal behavioral insight. It implies a read operation ('retrieve') but doesn't disclose critical traits like authentication requirements, rate limits, pagination, error handling, or whether it returns all folders or a subset. This leaves significant gaps for safe agent invocation.

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 front-loads the core action ('retrieve a list') without unnecessary words. Every part earns its place, making it easy to parse quickly.

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 no annotations, no output schema, and a parameter with 0% schema coverage, the description is incomplete. It lacks details on authentication, return format (e.g., folder structure, metadata), error cases, or limitations, which are essential for a tool interacting with user data.

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?

Schema description coverage is 0%, but the description adds no parameter details beyond implying a 'user's collection' context. It doesn't explain the 'username' parameter (e.g., format, whether it's a username or ID, or if it refers to the current user). With 1 parameter and low coverage, this is a baseline score with minimal added value.

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 ('retrieve') and resource ('list of folders in a user's collection'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_user_collection_folder' (singular) or 'get_user_collection_items', which could cause confusion about scope.

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., user authentication), compare to similar tools like 'get_user_collection_folder' (singular), or specify use cases like browsing vs. detailed folder access.

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