Skip to main content
Glama

Get Discogs Release

discogs_get_release
Read-only

Retrieve a Discogs release by release_id to inspect label, catalog number, format, country, year, tracklist, have/want counts, and master; use detailed mode for matrix/runout, barcode, and notes.

Instructions

Show the card of one Discogs Release (a specific pressing or edition) by its release_id.

Use it when the release_id is known, for example from discogs_search results, to see what exactly a pressing is: label, catalog number, Format, country, year, tracklist, how many Discogs users have or want it, and its Master. Ask for the detailed form to tell near-identical pressings apart by matrix/runout etchings, barcode and notes. Do not use it to find a Release by name (use discogs_search) or for prices (use discogs_get_prices).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "release_id": "<release_id>"
    },
    "name": "discogs_get_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
release_idYesDiscogs release_id, e.g. 249504.
response_formatNoconcise (default): label, catalog number, Format, country, year, tracklist, have/want and Master. detailed: adds identifiers (matrix/runout, barcode) and release notes.concise

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only and open-world behavior, so the safety profile is covered. The description adds useful behavioral context: what information the release card shows, and that the detailed form is needed to distinguish near-identical pressings by matrix/runout, barcode, and notes.

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 front-loaded with the core action, then usage context, then exclusions and alternatives. It is appropriately sized for a two-parameter lookup tool and every sentence contributes to correct selection or invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup with no output schema, the description explains the returned information and the effect of the concise versus detailed mode. It also routes the agent to the correct sibling tools, leaving no major ambiguity about when or how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters and the response_format enum are already well documented. The description still adds meaning by explaining where release_id typically comes from and giving a practical reason to request the detailed form beyond the schema's field list.

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

Purpose5/5

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

The description states a specific verb and resource: show one Discogs Release, identified as a specific pressing or edition, by release_id. It also distinguishes the tool from search and pricing siblings, so an agent can identify its role without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this when release_id is known, for example from discogs_search results. It also states when not to use it: not for finding a Release by name and not for prices, naming discogs_search and discogs_get_prices as alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.