Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

get_artist_releases

Retrieve an artist's discography from Discogs by providing the artist ID, with options to sort by year, title, or format and control pagination.

Instructions

Get an artist's releases

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artist_idYes
pageNo
per_pageNo
sortNo
sort_orderNo

Implementation Reference

  • Defines the MCP tool 'get_artist_releases' with its execute handler that delegates to ArtistService.getReleases and returns JSON stringified response.
    export const getArtistReleasesTool: Tool<FastMCPSessionAuth, typeof ArtistReleasesParamsSchema> = {
      name: 'get_artist_releases',
      description: `Get an artist's releases`,
      parameters: ArtistReleasesParamsSchema,
      execute: async (args) => {
        try {
          const artistService = new ArtistService();
          const artistReleases = await artistService.getReleases(args);
    
          return JSON.stringify(artistReleases);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Zod schema defining the input parameters for the get_artist_releases tool, merging artist_id with query params.
    export const ArtistReleasesParamsSchema = ArtistIdParamSchema.merge(
      QueryParamsSchema(['year', 'title', 'format'] as const),
    );
  • Function that registers all database-related tools, including getArtistReleasesTool, on the FastMCP server.
    export function registerDatabaseTools(server: FastMCP): void {
      server.addTool(getReleaseTool);
      server.addTool(getReleaseRatingTool);
      server.addTool(editReleaseRatingTool);
      server.addTool(deleteReleaseRatingTool);
      server.addTool(getReleaseCommunityRatingTool);
      server.addTool(getMasterReleaseTool);
      server.addTool(getMasterReleaseVersionsTool);
      server.addTool(getArtistTool);
      server.addTool(getArtistReleasesTool);
      server.addTool(getLabelTool);
      server.addTool(getLabelReleasesTool);
      server.addTool(searchTool);
    }
  • Implementation in ArtistService that performs the HTTP request to Discogs API endpoint for retrieving the artist's releases, validates response, and handles errors.
    async getReleases({ artist_id, ...options }: ArtistReleasesParams): Promise<ArtistReleases> {
      try {
        const response = await this.request<ArtistReleases>(`/${artist_id}/releases`, {
          params: options,
        });
    
        const validatedResponse = ArtistReleasesSchema.parse(response);
        return validatedResponse;
      } catch (error) {
        if (isDiscogsError(error)) {
          throw error;
        }
    
        throw new Error(`Failed to get artist releases: ${String(error)}`);
      }
    }
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Get') without any details on rate limits, authentication needs, pagination behavior (implied by 'page' and 'per_page' parameters but not explained), or what the return format looks like (e.g., list of objects with fields). This leaves critical operational traits unspecified.

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 extremely concise with a single sentence, 'Get an artist's releases', which is front-loaded and wastes no words. While this brevity contributes to under-specification in other dimensions, it earns full marks for conciseness as every word directly states the tool's purpose without redundancy.

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 with 0% schema coverage, no annotations, and no output schema), the description is incomplete. It doesn't cover parameter meanings, behavioral traits like pagination or authentication, or return values. For a tool with multiple parameters and no structured support, this minimal description leaves too many gaps for effective agent 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?

Schema description coverage is 0%, meaning none of the 5 parameters have descriptions in the schema. The tool description adds no information about parameters beyond what's inferred from their names (e.g., 'artist_id' for identifying the artist, 'page' for pagination). It doesn't explain the meaning of 'sort' options (e.g., 'year', 'title', 'format') or default behaviors, failing to compensate for the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get an artist's releases' clearly states the verb ('Get') and resource ('artist's releases'), making the purpose understandable. However, it lacks specificity about what 'releases' entails (e.g., albums, singles) and doesn't differentiate from sibling tools like 'get_artist' or 'get_label_releases', which could cause confusion. It's not tautological but remains somewhat vague.

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. For example, it doesn't mention how it differs from 'get_artist' (which might provide artist info without releases) or 'search' (which could find releases more broadly). There's no context on prerequisites or exclusions, leaving the agent to infer usage from the tool 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