Skip to main content
Glama

List Releases of a Discogs Master

discogs_list_master_releases
Read-only

List all pressings, versions, and editions of a Discogs master to compare them by country, year, label, catalog number, or format. Filter and sort results to find the release ID you need.

Instructions

List the Releases of a Discogs Master: all pressings, versions and editions of an album.

Use it to compare the available editions of an album by country, year, label, catalog number and Format, narrowed to one Format, country or year. Each line carries the release_id for discogs_get_release. Results are sorted by release date unless another sort is asked for, and paged. Find the master_id with discogs_search (type="master") or on a Release card.

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": {
      "master_id": "<master_id>"
    },
    "name": "discogs_list_master_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of Releases, from 1.
sortNoOrder of the list: released (default, oldest first), title, format, label, catno or country.released
yearNoOnly this release year.
limitNoReleases per page.
formatNoOnly this Format, exactly as Discogs writes it: Vinyl, CD, 7".
countryNoOnly Releases from this country, exactly as Discogs writes it: UK.
master_idYesDiscogs master_id, e.g. 96559.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description adds genuinely new behavior: results are sorted by release date unless another sort is requested, the list is paged, and each line carries a release_id for follow-up calls. It does not mention how pagination metadata (total pages/items) is returned or what happens for an invalid master_id, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded and well organized into purpose, usage, output shape and prerequisite discovery. There is minor redundancy between 'compare the available editions ... by country, year, label, catalog number and Format' and the following 'narrowed to one Format, country or year' sentence, but nothing is wasted enough to obscure the message.

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

Completeness4/5

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

For a 7-parameter read-only list tool with no output schema, the description covers purpose, filters, sort default, paging and the key returned field (release_id). It stops short of describing pagination metadata or error behavior, which would be the remaining gaps for an agent calling this blind.

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 coverage is 100%, so the schema already documents master_id, page, limit, sort, format, year and country with defaults and examples. The description mainly restates the filterable dimensions and adds only the mild clarification that narrowing is to a single Format, country or year at a time, so the baseline 3 applies.

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 opens with a specific verb and resource ('List the Releases of a Discogs Master') and immediately clarifies what those releases are ('all pressings, versions and editions of an album'). That framing distinguishes it cleanly from discogs_get_release (a single release) and discogs_search (which finds the master_id).

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 states the concrete use case (comparing editions by country, year, label, catalog number, Format), notes the narrowing behavior, and explicitly hands off to discogs_get_release for per-release detail. It also explains the prerequisite: obtain master_id via discogs_search with type="master" or from a Release card.

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