Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

get_label_releases

Retrieve releases associated with a specific label from the Discogs music database to explore catalog content and manage collections.

Instructions

Returns a list of Releases associated with the label

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
label_idYes
pageNo
per_pageNo
sortNo
sort_orderNo

Implementation Reference

  • The tool object definition including the execute handler function that performs the core logic by calling LabelService.getReleases.
    export const getLabelReleasesTool: Tool<FastMCPSessionAuth, typeof LabelReleasesParamsSchema> = {
      name: 'get_label_releases',
      description: 'Returns a list of Releases associated with the label',
      parameters: LabelReleasesParamsSchema,
      execute: async (args) => {
        try {
          const labelService = new LabelService();
          const labelReleases = await labelService.getReleases(args);
    
          return JSON.stringify(labelReleases);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod schema for input parameters of the get_label_releases tool, merging label ID and query params.
    /**
     * Schema for label releases parameters
     */
    export const LabelReleasesParamsSchema = LabelIdParamSchema.merge(QueryParamsSchema());
  • Registration of the get_label_releases tool with the FastMCP server.
    server.addTool(getLabelReleasesTool);
  • Supporting method in LabelService that fetches releases for a label from the Discogs API, called by the tool handler.
    async getReleases({ label_id, ...params }: LabelReleasesParams): Promise<LabelReleases> {
      try {
        const response = await this.request<LabelReleases>(`/${label_id}/releases`, {
          params,
        });
    
        const validatedResponse = LabelReleasesSchema.parse(response);
        return validatedResponse;
      } catch (error) {
        if (isDiscogsError(error)) {
          throw error;
        }
    
        throw new Error(`Failed to get label releases: ${String(error)}`);
      }
    }
  • Base schema for label ID parameter, merged into LabelReleasesParamsSchema.
    export const LabelIdParamSchema = z.object({
      label_id: z.number(),
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'Returns a list' but doesn't disclose behavioral traits like pagination handling (implied by 'page' and 'per_page' parameters), rate limits, authentication needs, or error conditions. This is a significant gap for a tool with multiple parameters.

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 no wasted words. It's front-loaded with the core purpose, 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 the complexity (5 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return format, pagination behavior, or how parameters interact, which is inadequate for a tool with multiple inputs and no structured output 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?

Schema description coverage is 0%, so the description must compensate. It only mentions 'label_id' implicitly ('associated with the label'), but doesn't explain the other 4 parameters (page, per_page, sort, sort_order) or their semantics. This leaves most parameters undocumented.

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 ('Returns a list') and resource ('Releases associated with the label'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_artist_releases' or 'get_master_release_versions', which also return releases but for different entities.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention how it differs from 'search' for finding releases or 'get_user_collection_items' for user-specific releases, leaving the agent to 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