Skip to main content
Glama

musicbrainz-mcp-server

by io.github.cyanheads

musicbrainz-mcp-server: get release group

musicbrainz_get_release_group
Read-onlyIdempotent

Release-group ("the album" above specific pressings) by MBID: primary type (Album/Single/EP) and secondary types (Live/Compilation), first-release date, artist credit, the list of releases (editions), tags/genres, and a cover-art availability flag from the WS/2 payload (use musicbrainz_get_cover_art for actual image URLs). The embedded releases list is capped at one page (25); for the complete set of editions, call musicbrainz_browse_entities with target_type=release and link.release-group. For a specific edition's tracklist, take a release MBID from the releases list and call musicbrainz_get_release.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mbidYesRelease-group MBID (36-character UUID).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
capNoThe one-page cap that was applied. Absent when not truncated.
mbidNoRelease-group MBID.
tagsNoCommunity tags/genres (may be empty).
errorNoPresent when the call failed. Absent on success.
shownNoNumber of releases returned. Absent when not truncated.
titleNoRelease-group title.
noticeNoHow to fetch the complete list of editions when truncated.
coverArtNoWhether cover art exists (availability stub from WS/2).
releasesNoReleases (editions) in this group (one page; may be empty or capped — use browse for all).
truncatedNoTrue when the releases list hit the one-page cap and more editions exist. Absent when the full set fit in one page.
primaryTypeNoPrimary type (Album, Single, EP, Broadcast, Other). Omitted when absent.
artistCreditNoCredited artists (may be empty).
disambiguationNoShort qualifier. Omitted when absent.
secondaryTypesNoSecondary types (Live, Compilation, Soundtrack, …). Omitted when none.
firstReleaseDateNoEarliest release date across all editions. Omitted when absent.
artistCreditStringNoDisplay string of the artist credit with join phrases.

TDQS

A4.7/5.0
Behavior5/5

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

Despite annotations already indicating read-only, open-world, and idempotent behavior, the description Adds significant context: the releases list is limited to one page (25), only a cover-art availability flag is returned (not URLs), and the distinction between release group and release is clarified. This exceeds the annotation coverage.

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, well-structured paragraph that front-loads the core purpose and then provides critical limitations and cross-references. Every sentence adds value with no redundancy or filler.

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?

Given the tool has only one parameter and an output schema is present, the description fully covers what the tool returns, the limitation, and how to extend functionality via sibling tools. It is complete for an agent to decide when and how to use it.

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?

The sole parameter (mbid) is fully described in the schema as 'Release-group MBID (36-character UUID).' The description simply says 'by MBID' without adding new format or usage details beyond the schema, meeting the baseline for 100% schema coverage.

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 clearly states the tool retrieves a release group by MBID and enumerates the specific data returned (primary/secondary types, release date, artist credit, releases list, tags/genres, cover-art flag). It distinguishes itself from siblings by explicitly naming alternative tools for cover art, browsing all releases, and getting tracklists.

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?

Provides explicit guidance on when to use alternatives: musicbrainz_get_cover_art for actual image URLs, musicbrainz_browse_entities for the full set of editions, and musicbrainz_get_release for tracklists. Also notes the embedded release list is capped at 25, prompting use of the browse tool when more are needed.

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

All musicbrainz-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a distinct purpose: browsing for paginated lists, getting individual entities, resolving identifiers, and text search. No overlap in functionality.

Naming Consistency5/5

All tools follow the musicbrainz_ prefix with clear verb-noun patterns (browse_entities, get_artist, lookup_identifier, search_entities), providing a consistent and predictable interface.

Tool Count5/5

With 10 tools covering all core MusicBrainz entity types, pagination, identifier resolution, and search, the count is well-scoped for a comprehensive API without being excessive.

Completeness5/5

The set covers all primary entity types (artist, label, recording, release, release-group, work), plus browsing, searching, identifier lookup, and cover art—providing a complete surface for MusicBrainz operations.

Resources