musicbrainz-mcp-server

Name: musicbrainz-mcp-server
Author: cyanheads

Server Details

Search MusicBrainz artists, releases, works, labels; resolve ISRC/ISWC/barcode; fetch cover art.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-09 08:22
Transport: Streamable HTTP
URL
Repository: cyanheads/musicbrainz-mcp-server
GitHub Stars: 1
Server Listing: musicbrainz-mcp-server

TDQS

A4.6/5.0

Scored 2026-08-22 04:00 across 10 tools

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.

Available Tools

10 tools

musicbrainz_browse_entitiesmusicbrainz-mcp-server: browse entitiesA

Read-onlyIdempotent

Inspect

Paginate the COMPLETE set of entities linked to a parent MBID — every release-group by an artist, every release on a label, every recording of a work, every release in a release-group. This is the only complete-enumeration path: the get_* tools embed at most one page (25) of any linked list, so use this tool whenever a linked set may exceed a page (a prolific artist, a major label with thousands of releases, a heavily-covered work). Provide exactly ONE link MBID matching a valid parent→child relationship for the target_type. Pages arbitrarily deep via offset; totalCount is the true upstream total.

ParametersJSON Schema

Name	Required	Description
`link`	Yes	Exactly one parent MBID. The valid key depends on target_type (see the description).
`limit`	No	Page size (1–100).
`offset`	No	Result offset for deep pagination (0-based).
`target_type`	Yes	The entity type to enumerate (the children).

Output Schema

ParametersJSON Schema

Name	Required	Description
`cap`	No	The page size that was applied. Absent when not truncated.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of entities returned in this page. Absent when not truncated.
`notice`	No	How to page further when results remain, or guidance when empty.
`offset`	No	The offset used for this page.
`entities`	No	This page of linked entities, in upstream order.
`linkMbid`	No	The parent MBID that was browsed.
`linkType`	No	The parent link type used (artist, label, release-group, recording, work, or area).
`truncated`	No	True when more entities remain beyond this page (offset + shown < totalCount). Absent when the page is complete.
`targetType`	No	The entity type that was enumerated.
`totalCount`	No	True total number of linked entities upstream (the {type}-count field).

TDQS

A5/5.0

Behavior5/5

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

The annotations already signal read-only, open-world, and idempotent behavior; the description adds valuable operational details like deep pagination via offset, totalCount as the true upstream total, and the exact-one-link requirement. Nothing contradicts the annotations.

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 purpose, then moves directly to when to use it, constraints, and pagination behavior. Every sentence contributes meaningful guidance with no 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?

This is a moderately complex tool with nested link objects, enums, and pagination; the description provides enough context to use it effectively and safely. The output schema and detailed annotations fill in the remaining structured details.

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

Parameters5/5

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

The input schema has 100% description coverage, and the main description strengthens understanding by requiring exactly one link MBID and clarifying parent-child relationships. Offset and limit semantics are also explained beyond their schema defaults.

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 names a specific action—paginate the COMPLETE set of entities linked to a parent MBID—and gives concrete examples across target types. It also differentiates itself from the get_* siblings by explicitly being the only complete-enumeration path.

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 provides an explicit when-to-use rule: whenever a linked set may exceed the single 25-item page returned by get_* tools. It also states the main constraint—exactly one link MBID and a valid parent-child relationship—which helps prevent incorrect invocations.

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

musicbrainz_get_artistmusicbrainz-mcp-server: get artistA

Read-onlyIdempotent

Inspect

Artist profile by MBID: type (person/group/…), country, life span, gender, area, aliases, tags/genres, plus the discography (release-groups) and band-membership / collaboration relationships and external links (Wikidata QID, Discogs, official site — surfaced as url-rels chainable to those servers). The 80% artist-detail call. Discography and relationships are capped at one page (25); for a prolific artist's complete release-group list, call musicbrainz_browse_entities with target_type=release-group and the artist link.

ParametersJSON Schema

Name	Required	Description
`mbid`	Yes	Artist MBID (36-character UUID).
`inc_relationships`	No	Include band-membership / collaboration relationships and external links (url-rels).
`inc_release_groups`	No	Include the discography (release-groups). Capped at one page; use browse for the full set.

Output Schema

ParametersJSON Schema

Name	Required	Description
`cap`	No	The one-page cap that was applied. Absent when not truncated.
`area`	No	Associated area name. Omitted when unknown.
`mbid`	No	Artist MBID.
`name`	No	Artist name.
`tags`	No	Community tags/genres with vote counts (may be empty).
`type`	No	Artist type (Person, Group, Orchestra, …). Omitted when unknown.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of release-groups returned. Absent when not truncated.
`gender`	No	Gender, for person-type artists. Omitted when unknown/inapplicable.
`notice`	No	How to fetch the complete discography when truncated.
`aliases`	No	Alternate names (may be empty).
`country`	No	ISO country code. Omitted when unknown.
`lifeSpan`	No	Birth/death or formation/dissolution span. Omitted when unknown.
`sortName`	No	Sortable name form. Omitted when absent.
`truncated`	No	True when the discography hit the one-page cap and more release-groups exist. Absent when the full set fit in one page.
`externalLinks`	No	External resource links (url-rels) — Wikidata, Discogs, official site (may be empty).
`relationships`	No	Band membership and collaboration relationships (may be empty).
`releaseGroups`	No	Discography — release-groups (one page; may be empty or capped).
`disambiguation`	No	Short qualifier distinguishing same-named artists. Omitted when absent.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld hints, so the description does not need to restate safety. It adds useful behavioral context: the one-page cap, the content included in the profile, and that external links are url-rels chainable to external servers. No annotation contradiction exists.

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 purpose, followed by key content details and the important limitation/alternative. Three sentences cover what the tool returns, its scope, and when to switch tools; no sentence is wasted or redundant.

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 read-only artist lookup with a rich output schema and strong annotations, the description is complete. It covers the primary use case, the data returned, the pagination cap, and an alternative for extended results, so an agent can confidently select and invoke the tool without needing additional context.

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 description coverage is 100%, so the schema already documents mbid and the two boolean flags thoroughly. The description repeats the cap and browse alternative already present in the inc_release_groups parameter description, but does not add new parameter-level meaning beyond the schema, warranting the baseline score.

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 'Artist profile by MBID' and enumerates concrete content: type, country, life span, gender, area, aliases, tags/genres, discography, relationships, and external links. It also distinguishes itself from siblings by identifying itself as 'The 80% artist-detail call' and pointing to browse_entities for the complete list.

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?

Usage context is explicit: this is the go-to artist-detail call, with a clear caveat that discography and relationships are capped at one page (25). For a full release-group list, the description explicitly directs the agent to musicbrainz_browse_entities with target_type=release-group and the artist link, providing a concrete alternative.

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

musicbrainz_get_cover_artmusicbrainz-mcp-server: get cover artA

Read-onlyIdempotent

Inspect

Cover Art Archive images for a release or release-group MBID: front/back flags, image types, full-resolution URLs, and 250/500/1200px thumbnail URLs. Returns an empty image set (NOT an error) when the entity has no art — absence of art is information. Art is served at the release level; a release-group MBID resolves to a representative release's art automatically. URLs are linked, never rehosted — image copyright stays with the rights holders (only MusicBrainz core metadata is CC0).

ParametersJSON Schema

Name	Required	Description	Default
`mbid`	Yes	Release or release-group MBID (36-character UUID).
`entity_type`	No	Whether the MBID is a release (default) or a release-group.	release

Output Schema

ParametersJSON Schema

Name	Required	Description
`mbid`	No	The MBID that was queried.
`error`	No	Present when the call failed. Absent on success.
`hasArt`	No	Whether any cover art exists for this entity.
`images`	No	Cover-art images (empty when the entity has no art).
`notice`	No	Notice when no art exists for the entity.
`entityType`	No	Whether the MBID was treated as a release or release-group.
`representativeRelease`	No	For a release-group query, the release MBID whose art was returned. Omitted for direct release queries.

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare the tool read-only and idempotent, and the description adds valuable non-obvious behavior beyond those hints: empty results are meaningful information rather than errors, art is always served at the release level, and linked URLs are not rehosted. The copyright/CC0 note also explains an important legal implication.

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 compact and content-dense. Each sentence carries meaningful information: outputs, empty-set behavior, release-group resolution, and rights/linking semantics. There is no filler or repetition of schema content.

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 read-only lookup tool with rich parameter and output schema coverage, the description covers essential edge cases and nuances: empty art sets, release-group auto-resolution, and non-rehosted image URLs. The agent has enough context to invoke the tool correctly and even to interpret unusual responses.

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%, and both parameters are already described in the schema. The description reinforces the release/release-group MBID distinction and explains release-group resolution, but it does not substantially add syntax or format details beyond what the schema provides, making the schema baseline of 3 appropriate.

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 identifies the tool as retrieving Cover Art Archive images for a release or release-group MBID and specifies the exact kinds of information returned: front/back flags, image types, full-resolution URLs, and thumbnail URLs. It is distinct from sibling entity-specific lookup tools because it targets art rather than core metadata.

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

Usage Guidelines4/5

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

The description gives clear usage context: accepts release or release-group MBIDs, automatically resolves release-group MBIDs to a representative release, and returns an empty set instead of an error when no art exists. It does not explicitly compare to sibling tools, but the purpose and behavior are specific enough for an agent to select this tool appropriately.

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

musicbrainz_get_labelmusicbrainz-mcp-server: get labelA

Read-onlyIdempotent

Inspect

Label by MBID: type (Original Production, Reissue, Imprint, …), country, life span, label code (the LC number), area, aliases, tags, and external links (url-rels — Wikidata, Discogs, official site). A label's releases are a potentially huge linked set (a major label can have tens of thousands), so they are NOT embedded here — enumerate them with musicbrainz_browse_entities (target_type=release, link.label).

ParametersJSON Schema

Name	Required	Description	Default
`mbid`	Yes	Label MBID (36-character UUID).

Output Schema

ParametersJSON Schema

Name	Required	Description
`area`	No	Associated area name. Omitted when unknown.
`mbid`	No	Label MBID.
`name`	No	Label name.
`tags`	No	Community tags/genres (may be empty).
`type`	No	Label type. Omitted when unknown.
`error`	No	Present when the call failed. Absent on success.
`aliases`	No	Alternate names (may be empty).
`country`	No	ISO country code. Omitted when unknown.
`lifeSpan`	No	Founding/dissolution span. Omitted when unknown.
`sortName`	No	Sortable name form. Omitted when absent.
`labelCode`	No	Label code (LC number), without the "LC" prefix. Omitted when absent.
`externalLinks`	No	External resource links (url-rels) (may be empty).
`disambiguation`	No	Short qualifier. Omitted when absent.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description only needs to add extra context. It adds that releases are excluded due to size and that they can be browsed separately, which is important behavioral disclosure not captured by annotations. No contradiction with annotations.

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 two sentences: the first lists the returned fields, the second explains the release exclusion and points to an alternative. It is front-loaded, informative, and contains no fluff.

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 single-parameter lookup tool with an output schema, the description fully covers what the tool returns, what it excludes, and how to get the excluded data. Combined with annotations, it provides complete guidance for effective use.

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 description coverage is 100%, so the schema already documents 'mbid' as 'Label MBID (36-character UUID)'. The description only repeats 'by MBID' without adding new parameter semantics, yielding the baseline score for high 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 'Label by MBID' and lists the specific data fields (type, country, life span, label code, area, aliases, tags, external links). It distinguishes from sibling tools by focusing on the label entity and explicitly notes that releases are not included, differentiating from browse_entities.

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?

The description explicitly says 'they are NOT embedded here — enumerate them with musicbrainz_browse_entities (target_type=release, link.label)', providing a clear when-not-to-use and naming the alternative tool. It also implies when to use this tool (when label details are needed) implicitly.

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

musicbrainz_get_recordingmusicbrainz-mcp-server: get recordingA

Read-onlyIdempotent

Inspect

Recording (a specific performance/track, distinct from the abstract work) by MBID: length, artist credits, ISRCs, the releases it appears on, the work(s) it performs (work-rels — chain to musicbrainz_get_work), and performance/production relationships (who played, produced, engineered, conducted — each with the role and the credited artist MBID). Relationships are capped at one page; for a heavily-covered recording call musicbrainz_browse_entities with target_type=recording and link.work.

ParametersJSON Schema

Name	Required	Description	Default
`mbid`	Yes	Recording MBID (36-character UUID).
`inc_relationships`	No	Include performance/production relationships (performers, producers, engineers) and work-rels.

Output Schema

ParametersJSON Schema

Name	Required	Description
`mbid`	No	Recording MBID.
`error`	No	Present when the call failed. Absent on success.
`isrcs`	No	ISRCs assigned to this recording (may be empty).
`title`	No	Recording title.
`length`	No	Recording length as m:ss. Omitted when unknown.
`releases`	No	Releases this recording appears on (may be empty).
`artistCredit`	No	Credited artists (may be empty).
`externalLinks`	No	External resource links (url-rels) (may be empty).
`relationships`	No	Performance/production relationships and work-rels (may be empty).
`disambiguation`	No	Short qualifier. Omitted when absent.
`firstReleaseDate`	No	Earliest release date for this recording. Omitted when absent.
`artistCreditString`	No	Display string of the artist credit with join phrases.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering safety. The description adds behavioral context beyond these by stating that relationships are capped at one page, which is a significant limitation, and mentions the pagination alternative. It also clarifies the scope of included relationships and the role of MBIDs. No contradiction with annotations.

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?

The description is a single, dense sentence that front-loads the purpose and then lists content. It manages to include all key behavioral and contextual details without redundancy. While it is longer than average, every phrase contributes information, and the structure (purpose, contents, limitation/alternative) is logical. Not overly verbose.

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 that an output schema exists (has output schema: true), the description need not explain return format. It covers the tool's inputs, what data is returned, the pagination cap, and the recommended alternative for heavy cases. Combined with the rich annotations, the description is fully complete for a read-only lookup tool.

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 schema description covers 100% of parameters (mbid and inc_relationships) with clear descriptions. The tool description adds minimal parameter-specific insight beyond reinforcing 'by MBID' and linking work-rels, but it does not need to because the schema already documents the parameters adequately. This meets the baseline of 3.

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 it retrieves a recording (a specific performance/track) by MBID, distinguishing it from the abstract work. It enumerates the specific data returned (length, credits, ISRCs, releases, works, relationships), making the tool's function unambiguous and differentiating it from sibling get_* tools.

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?

The description provides explicit usage context by identifying the tool as for recordings by MBID and includes an explicit alternative: 'for a heavily-covered recording call musicbrainz_browse_entities with target_type=recording and link.work.' It also implies a chaining pattern via 'work-rels — chain to musicbrainz_get_work', indicating when to use that sibling.

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

musicbrainz_get_releasemusicbrainz-mcp-server: get releaseA

Read-onlyIdempotent

Inspect

One edition's full detail by MBID: the tracklist (media → tracks → recordings with lengths and recording MBIDs), label + catalog number, barcode, country, release date, format, packaging, text representation (language/script), and a cover-art availability stub. Track lengths are rendered m:ss (stored as milliseconds upstream). For the actual cover image URLs, call musicbrainz_get_cover_art with this release MBID.

ParametersJSON Schema

Name	Required	Description	Default
`mbid`	Yes	Release MBID (36-character UUID).

Output Schema

ParametersJSON Schema

Name	Required	Description
`date`	No	Release date. Omitted when absent.
`mbid`	No	Release MBID.
`error`	No	Present when the call failed. Absent on success.
`media`	No	Media (discs) with their tracklists (may be empty).
`title`	No	Release title.
`script`	No	Text-representation script code. Omitted when absent.
`status`	No	Release status (Official, Promotion, Bootleg, …). Omitted when absent.
`barcode`	No	Barcode (UPC/EAN). Omitted when absent; empty string upstream means "known to have none".
`country`	No	Release country code. Omitted when absent.
`coverArt`	No	Whether cover art exists (availability stub from WS/2).
`language`	No	Text-representation language code. Omitted when absent.
`labelInfo`	No	Label / catalog-number pairings (may be empty).
`packaging`	No	Packaging type (Jewel Case, Digipak, …). Omitted when absent.
`artistCredit`	No	Credited artists (may be empty).
`disambiguation`	No	Short qualifier. Omitted when absent.
`releaseGroupId`	No	Parent release-group MBID — chain to musicbrainz_get_release_group. Omitted when absent.
`artistCreditString`	No	Display string of the artist credit with join phrases.

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already include readOnlyHint=true, openWorldHint=true, and idempotentHint=true, indicating a safe read operation. The description adds value beyond that by disclosing that track lengths are converted from milliseconds to m:ss format, a behavioral detail not in annotations, and noting a 'cover-art availability stub' (not actual images), which sets expectations. No contradictions.

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 concise and front-loaded: it opens with a clear purpose, lists key data items in a parenthetical, and ends with a specific redirect to a sibling tool. Every sentence serves a purpose (purpose, data details, format note, alternative usage), with no fluff or repetition.

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?

The tool is simple (one parameter) with strong annotations and an output schema present. The description covers all essential aspects: what data is returned, units conversion, and how to get cover art. It is complete for the tool's complexity, and the output schema handles return value details, so nothing essential is missing.

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?

The schema already covers 100% of the single parameter with a clear description ('Release MBID (36-character UUID).'). The description adds context by referencing 'this release MBID' in the cover art instruction, reinforcing the parameter's role. Since schema coverage is high and description adds minimal but useful context, a 4 is appropriate; it exceeds the baseline 3 by clarifying the parameter's usage.

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 what the tool does: 'One edition's full detail by MBID' and enumerates the specific data returned (tracklist, label, catalog number, barcode, etc.). It distinguishes itself from siblings by explicitly pointing to musicbrainz_get_cover_art for actual cover images, and is distinct from other get_* tools by focusing on release-specific data.

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?

The description explicitly includes usage guidance: 'For the actual cover image URLs, call musicbrainz_get_cover_art with this release MBID.' This tells the agent when to use a different tool, which is clear and helpful. It also implies use when a specific release's full details are needed, and the covered fields set a clear scope.

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

musicbrainz_get_release_groupmusicbrainz-mcp-server: get release groupA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`mbid`	Yes	Release-group MBID (36-character UUID).

Output Schema

ParametersJSON Schema

Name	Required	Description
`cap`	No	The one-page cap that was applied. Absent when not truncated.
`mbid`	No	Release-group MBID.
`tags`	No	Community tags/genres (may be empty).
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of releases returned. Absent when not truncated.
`title`	No	Release-group title.
`notice`	No	How to fetch the complete list of editions when truncated.
`coverArt`	No	Whether cover art exists (availability stub from WS/2).
`releases`	No	Releases (editions) in this group (one page; may be empty or capped — use browse for all).
`truncated`	No	True when the releases list hit the one-page cap and more editions exist. Absent when the full set fit in one page.
`primaryType`	No	Primary type (Album, Single, EP, Broadcast, Other). Omitted when absent.
`artistCredit`	No	Credited artists (may be empty).
`disambiguation`	No	Short qualifier. Omitted when absent.
`secondaryTypes`	No	Secondary types (Live, Compilation, Soundtrack, …). Omitted when none.
`firstReleaseDate`	No	Earliest release date across all editions. Omitted when absent.
`artistCreditString`	No	Display 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.

musicbrainz_get_workmusicbrainz-mcp-server: get workA

Read-onlyIdempotent

Inspect

Work (a composition — the song as written, distinct from any specific recording) by MBID: type, language(s), ISWCs (the work-level standard identifier), writer/composer/lyricist relationships (with the credited artist MBID), aliases, tags, and the recordings that perform it. The recording relationships are returned in full (the work lookup does not page them).

ParametersJSON Schema

Name	Required	Description	Default
`mbid`	Yes	Work MBID (36-character UUID).
`inc_relationships`	No	Include writer/composer relationships, recording relationships, and external links.

Output Schema

ParametersJSON Schema

Name	Required	Description
`mbid`	No	Work MBID.
`tags`	No	Community tags/genres (may be empty).
`type`	No	Work type (Song, Symphony, …). Omitted when unknown.
`error`	No	Present when the call failed. Absent on success.
`iswcs`	No	ISWCs assigned to this work (may be empty).
`title`	No	Work title.
`aliases`	No	Alternate titles (may be empty).
`languages`	No	Lyrics languages (ISO codes; may be empty).
`externalLinks`	No	External resource links (url-rels) (may be empty).
`relationships`	No	Writer/composer/lyricist relationships and recording-rels — the complete set (may be empty).
`disambiguation`	No	Short qualifier. Omitted when absent.

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds a valuable behavioral detail: 'The recording relationships are returned in full (the work lookup does not page them),' which goes beyond the annotations. This helps the agent understand the return behavior.

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?

The description is a single, dense sentence that front-loads the definition and then lists content. Every phrase adds value, with no filler. The list is long but compact, making it efficient if slightly dense.

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?

Given the presence of an output schema, annotations, and a detailed description, the tool is well-covered. The description covers the main return fields and the non-paging behavior. It could mention error handling or rate limits, but those are not specified and are likely covered elsewhere.

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% with both parameters described. The description repeats the list of included relationships but does not add new parameter-specific semantics. It clarifies the concept of a work but not the syntax or behavior of the parameters beyond the schema.

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 gets a work by MBID, defining 'work' as a composition distinct from recordings. It lists specific fields returned (type, languages, ISWCs, relationships, aliases, tags, recordings), which distinguishes it from sibling get_* tools for other entity types.

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

Usage Guidelines4/5

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

The description gives clear context for use: fetch a work by its MBID. It does not explicitly mention alternatives or exclusions, but the tool name and definition imply the appropriate use case. A more explicit 'use this instead of X when...' would make it a 5.

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

musicbrainz_lookup_identifiermusicbrainz-mcp-server: lookup identifierA

Read-onlyIdempotent

Inspect

Resolve a standard identifier to MusicBrainz entities without a name search — the deterministic path when you already hold an ID. id_type=isrc → recordings (a recording-level code, often shared by several recordings); id_type=iswc → works (a composition-level code); id_type=barcode → releases (UPC/EAN). ISRC and ISWC hit dedicated exact endpoints; barcode is a Lucene search filter so results are ranked (exact match scores 100). The output kind field tells you which entity type came back.

ParametersJSON Schema

Name	Required	Description	Default
`value`	Yes	The identifier value. ISRC e.g. "USRC17607839"; ISWC e.g. "T-010.140.236-1"; barcode e.g. "075678164125".
`id_type`	Yes	Which standard identifier: isrc (recording), iswc (work), or barcode (release).

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`result`	No	The resolved entities, discriminated by `kind` (recordings \| works \| releases).

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses meaningful behavior: ISRC and ISWC use dedicated exact endpoints while barcode uses a Lucene-ranked search, exact barcodes score 100, ISRCs may map to multiple recordings, and the returned 'kind' field identifies the entity type. This goes well beyond the annotations and gives the agent accurate expectations.

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 three sentences and front-loaded with the key purpose statement. Each sentence earns its place: the first defines the tool, the second maps identifier types to entities, and the third explains endpoint/search behavior and output semantics. No filler or redundancy.

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?

With only two well-documented parameters, a clear output schema, and rich annotations, the description covers the important contextual nuances: deterministic behavior, entity-type mapping, exact vs. ranked matching, and how to interpret the output. Nothing essential is missing for an agent to invoke this tool appropriately.

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?

The input schema already defines both parameters with descriptions and an enum for id_type, so the baseline is high. The description adds extra meaning by explaining the entity-level implications of each id_type and the underlying endpoint/search behavior, which is useful semantic context beyond the raw schema.

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 resolves standard identifiers to MusicBrainz entities 'without a name search' and is 'the deterministic path when you already hold an ID.' It distinguishes itself from sibling tools like musicbrainz_search_entities and the get_* family by framing this as ID-based lookup, and it lists the exact id_type to entity-type mappings.

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

Usage Guidelines4/5

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

It explicitly explains when to use the tool: 'when you already hold an ID' and 'without a name search.' It also gives per-identifier entity outcomes (ISRC → recordings, ISWC → works, barcode → releases), which helps select this over search/browse tools. It does not explicitly name alternatives, but the intended use context is clear.

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

musicbrainz_search_entitiesmusicbrainz-mcp-server: search entitiesA

Read-onlyIdempotent

Inspect

Full-text search across a MusicBrainz entity type (artist, release-group, release, recording, work, label) using a Lucene query string. Returns ranked matches with MBID, name/title, disambiguation, type, and a 0–100 relevance score (100 = exact). Starting point when resolving a name to an MBID — chain the returned MBID into the matching musicbrainz_get_* tool. Results are in MusicBrainz score-descending order. Supports field-scoped Lucene syntax (e.g. artist:radiohead AND country:GB).

ParametersJSON Schema

Name	Required	Description
`limit`	No	Maximum results to return (1–100).
`query`	Yes	Lucene query string. Plain text matches names/titles; field scoping (e.g. `artist:`, `country:`, `tag:`) is supported.
`offset`	No	Result offset for pagination (0-based).
`entityType`	Yes	Which entity type to search.

Output Schema

ParametersJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Guidance when zero results matched — how to broaden or correct the query.
`results`	No	Ranked matches, in MusicBrainz score-descending order.
`entityType`	No	The entity type that was searched.
`totalCount`	No	Total matches upstream before the limit/offset window.
`effectiveQuery`	No	The query string as sent to MusicBrainz.

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds behavioral details beyond that: ranked matches with specific fields (MBID, name/title, disambiguation, type) and a 0–100 relevance score, plus ordering by score descending. It also mentions Lucene field-scoped syntax. This adds value without contradicting annotations.

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 two sentences, front-loaded with the core purpose, and each sentence carries useful information: what it does, what it returns, when to use it, and supported syntax. There is no fluff or repetition of schema details.

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?

The tool is moderately complex (Lucene search) and has an output schema, so the description doesn't need to detail every return field. It explains the return fields, ordering, and usage context sufficiently. Given the annotations and schema coverage, the description is complete for guiding selection and invocation.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by giving a concrete Lucene example (`artist:radiohead AND country:GB`) and clarifying that plain text matches names/titles. It also explains the relevance score semantics (100 = exact), which is not in the schema. This provides extra context for agents constructing queries.

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 performs full-text search across a specific MusicBrainz entity type using a Lucene query string, with a specific verb and resource. It distinguishes from siblings by noting it is the starting point for name-to-MBID resolution, and the sibling set includes browse and get tools which serve different purposes (browse and ID-based retrieval).

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: 'Starting point when resolving a name to an MBID — chain the returned MBID into the matching musicbrainz_get_* tool.' This tells the agent when to use it and how to follow up. It also implies alternatives (browse/get tools) without naming them explicitly, but the chaining instruction is clear and actionable.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

10 tool updatesAug 21, 2026

Changedmusicbrainz_browse_entities6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "targetType",
+      "linkType",
+      "linkMbid",
+      "entities",
+      "offset",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_link`: No link MBID was provided, more than one was provided, or the link MBID is malformed (HTTP 400). `entity_not_found`: The link MBID is well-formed but no such parent entity exists (HTTP 404). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_link",
+            "entity_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "targetType",
-  "linkType",
-  "linkMbid",
-  "entities",
-  "offset",
-  "totalCount"
-]

Changedmusicbrainz_get_artist6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "name",
+      "aliases",
+      "tags",
+      "releaseGroups",
+      "relationships",
+      "externalLinks"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (MusicBrainz returns HTTP 400). `entity_not_found`: The MBID is well-formed but no artist exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_mbid",
+            "entity_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "mbid",
-  "name",
-  "aliases",
-  "tags",
-  "releaseGroups",
-  "relationships",
-  "externalLinks"
-]

Changedmusicbrainz_get_cover_art6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "entityType",
+      "images",
+      "hasArt"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (the upstream returns HTTP 400). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_mbid"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "mbid",
-  "entityType",
-  "images",
-  "hasArt"
-]

Changedmusicbrainz_get_label6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "name",
+      "aliases",
+      "tags",
+      "externalLinks"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (MusicBrainz returns HTTP 400). `entity_not_found`: The MBID is well-formed but no label exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_mbid",
+            "entity_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "mbid",
-  "name",
-  "aliases",
-  "tags",
-  "externalLinks"
-]

Changedmusicbrainz_get_recording6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "title",
+      "artistCredit",
+      "artistCreditString",
+      "isrcs",
+      "releases",
+      "relationships",
+      "externalLinks"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (MusicBrainz returns HTTP 400). `entity_not_found`: The MBID is well-formed but no recording exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_mbid",
+            "entity_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "mbid",
-  "title",
-  "artistCredit",
-  "artistCreditString",
-  "isrcs",
-  "releases",
-  "relationships",
-  "externalLinks"
-]

Changedmusicbrainz_get_release6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "title",
+      "artistCredit",
+      "artistCreditString",
+      "labelInfo",
+      "media",
+      "coverArt"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (MusicBrainz returns HTTP 400). `entity_not_found`: The MBID is well-formed but no release exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_mbid",
+            "entity_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "mbid",
-  "title",
-  "artistCredit",
-  "artistCreditString",
-  "labelInfo",
-  "media",
-  "coverArt"
-]

Changedmusicbrainz_get_release_group6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "title",
+      "artistCredit",
+      "artistCreditString",
+      "releases",
+      "tags",
+      "coverArt"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (MusicBrainz returns HTTP 400). `entity_not_found`: The MBID is well-formed but no release-group exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_mbid",
+            "entity_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "mbid",
-  "title",
-  "artistCredit",
-  "artistCreditString",
-  "releases",
-  "tags",
-  "coverArt"
-]

Changedmusicbrainz_get_work6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "mbid",
+      "title",
+      "languages",
+      "iswcs",
+      "aliases",
+      "tags",
+      "relationships",
+      "externalLinks"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `invalid_mbid`: The MBID is malformed or the all-zeros sentinel (MusicBrainz returns HTTP 400). `entity_not_found`: The MBID is well-formed but no work exists with it (MusicBrainz returns HTTP 404). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "invalid_mbid",
+            "entity_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "mbid",
-  "title",
-  "languages",
-  "iswcs",
-  "aliases",
-  "tags",
-  "relationships",
-  "externalLinks"
-]

Changedmusicbrainz_lookup_identifier6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "result"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `identifier_not_found`: The identifier is well-formed but resolves to zero entities. `invalid_identifier`: The ISRC/ISWC is malformed (the dedicated endpoint returns HTTP 400). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "identifier_not_found",
+            "invalid_identifier"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```

Changedmusicbrainz_search_entities6 fields changed

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "entityType",
+      "results",
+      "effectiveQuery",
+      "totalCount"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode.",
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "entityType",
-  "results",
-  "effectiveQuery",
-  "totalCount"
-]

3 tool updatesJun 20, 2026

Changedmusicbrainz_get_release_group5 fields changed

addedOutput schema / properties / cap

Added value: +{
+  "description": "The one-page cap that was applied. Absent when not truncated.",
+  "type": "number"
+}

addedOutput schema / properties / notice

Added value: +{
+  "description": "How to fetch the complete list of editions when truncated.",
+  "type": "string"
+}

changedOutput schema / properties / releases / description

Previous value: -"Releases (editions) in this group (may be empty)."New value: +"Releases (editions) in this group (one page; may be empty or capped — use browse for all)."

addedOutput schema / properties / shown

Added value: +{
+  "description": "Number of releases returned. Absent when not truncated.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when the releases list hit the one-page cap and more editions exist. Absent when the full set fit in one page.",
+  "type": "boolean"
+}

Changedmusicbrainz_get_work5 fields changed

removedOutput schema / properties / cap

Removed value: -{
-  "description": "The one-page cap that was applied. Absent when not truncated.",
-  "type": "number"
-}

removedOutput schema / properties / notice

Removed value: -{
-  "description": "How to fetch the complete list of recordings of this work when truncated.",
-  "type": "string"
-}

changedOutput schema / properties / relationships / description

Previous value: -"Writer/composer/lyricist relationships and recording-rels (may be empty; recording-rels capped at one page)."New value: +"Writer/composer/lyricist relationships and recording-rels — the complete set (may be empty)."

removedOutput schema / properties / shown

Removed value: -{
-  "description": "Number of recording relationships returned. Absent when not truncated.",
-  "type": "number"
-}

removedOutput schema / properties / truncated

Removed value: -{
-  "description": "True when the recording relationships hit the one-page cap. Absent when the full set fit in one page.",
-  "type": "boolean"
-}

Changedmusicbrainz_lookup_identifier2 fields changed

changedInput schema / properties / value / description

Previous value: -"The identifier value. ISRC e.g. \"USRC17607839\"; ISWC e.g. \"T-345246800-1\"; barcode e.g. \"075678164125\"."New value: +"The identifier value. ISRC e.g. \"USRC17607839\"; ISWC e.g. \"T-010.140.236-1\"; barcode e.g. \"075678164125\"."

changedOutput schema / properties / result / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "description": "ISRC result arm: recordings carrying the ISRC.",
-    "properties": {
-      "identifier": {
-        "description": "The looked-up identifier value.",
-        "type": "string"
-      },
-      "kind": {
-        "const": "recordings",
-        "description": "ISRC resolved to recordings.",
-        "type": "string"
-      },
-      "recordings": {
-        "description": "Recordings carrying this ISRC.",
-        "items": {
-          "additionalProperties": false,
-          "description": "A recording carrying the looked-up ISRC.",
-          "properties": {
-            "artistCredit": {
-              "description": "Credited artist string.",
-              "type": "string"
-            },
-            "length": {
-              "description": "Recording length as m:ss. Omitted when unknown.",
-              "type": "string"
-            },
-            "mbid": {
-              "description": "Recording MBID — chain to musicbrainz_get_recording.",
-              "type": "string"
-            },
-            "title": {
-              "description": "Recording title.",
-              "type": "string"
-            }
-          },
-          "required": [
-            "mbid",
-            "title",
-            "artistCredit"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "kind",
-      "identifier",
-      "recordings"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "description": "ISWC result arm: works carrying the ISWC.",
-    "properties": {
-      "identifier": {
-        "description": "The looked-up identifier value.",
-        "type": "string"
-      },
-      "kind": {
-        "const": "works",
-        "description": "ISWC resolved to works.",
-        "type": "string"
-      },
-      "works": {
-        "description": "Works carrying this ISWC.",
-        "items": {
-          "additionalProperties": false,
-          "description": "A work carrying the looked-up ISWC.",
-          "properties": {
-            "mbid": {
-              "description": "Work MBID — chain to musicbrainz_get_work.",
-              "type": "string"
-            },
-            "title": {
-              "description": "Work title.",
-              "type": "string"
-            },
-            "type": {
-              "description": "Work type. Omitted when absent.",
-              "type": "string"
-            }
-          },
-          "required": [
-            "mbid",
-            "title"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "kind",
-      "identifier",
-      "works"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "description": "Barcode result arm: releases carrying the barcode.",
-    "properties": {
-      "identifier": {
-        "description": "The looked-up identifier value.",
-        "type": "string"
-      },
-      "kind": {
-        "const": "releases",
-        "description": "Barcode resolved to releases.",
-        "type": "string"
-      },
-      "releases": {
-        "description": "Releases carrying this barcode (ranked).",
-        "items": {
-          "additionalProperties": false,
-          "description": "A release carrying the looked-up barcode.",
-          "properties": {
-            "artistCredit": {
-              "description": "Credited artist string.",
-              "type": "string"
-            },
-            "country": {
-              "description": "Release country code. Omitted when absent.",
-              "type": "string"
-            },
-            "date": {
-              "description": "Release date. Omitted when absent.",
-              "type": "string"
-            },
-            "mbid": {
-              "description": "Release MBID — chain to musicbrainz_get_release.",
-              "type": "string"
-            },
-            "score": {
-              "description": "Lucene relevance score, 0–100 (barcode is a search filter; exact = 100).",
-              "type": "number"
-            },
-            "title": {
-              "description": "Release title.",
-              "type": "string"
-            }
-          },
-          "required": [
-            "mbid",
-            "title",
-            "artistCredit",
-            "score"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "kind",
-      "identifier",
-      "releases"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "description": "ISRC result arm: recordings carrying the ISRC.",
+    "properties": {
+      "identifier": {
+        "description": "The looked-up identifier value.",
+        "type": "string"
+      },
+      "kind": {
+        "const": "recordings",
+        "description": "ISRC resolved to recordings.",
+        "type": "string"
+      },
+      "recordings": {
+        "description": "Recordings carrying this ISRC.",
+        "items": {
+          "additionalProperties": false,
+          "description": "A recording carrying the looked-up ISRC.",
+          "properties": {
+            "artistCredit": {
+              "description": "Credited artist string; falls back to \"Unknown artist\" when none is recorded.",
+              "type": "string"
+            },
+            "length": {
+              "description": "Recording length as m:ss. Omitted when unknown.",
+              "type": "string"
+            },
+            "mbid": {
+              "description": "Recording MBID — chain to musicbrainz_get_recording.",
+              "type": "string"
+            },
+            "title": {
+              "description": "Recording title.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "mbid",
+            "title",
+            "artistCredit"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "kind",
+      "identifier",
+      "recordings"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "ISWC result arm: works carrying the ISWC.",
+    "properties": {
+      "identifier": {
+        "description": "The looked-up identifier value.",
+        "type": "string"
+      },
+      "kind": {
+        "const": "works",
+        "description": "ISWC resolved to works.",
+        "type": "string"
+      },
+      "works": {
+        "description": "Works carrying this ISWC.",
+        "items": {
+          "additionalProperties": false,
+          "description": "A work carrying the looked-up ISWC.",
+          "properties": {
+            "mbid": {
+              "description": "Work MBID — chain to musicbrainz_get_work.",
+              "type": "string"
+            },
+            "title": {
+              "description": "Work title.",
+              "type": "string"
+            },
+            "type": {
+              "description": "Work type. Omitted when absent.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "mbid",
+            "title"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "kind",
+      "identifier",
+      "works"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Barcode result arm: releases carrying the barcode.",
+    "properties": {
+      "identifier": {
+        "description": "The looked-up identifier value.",
+        "type": "string"
+      },
+      "kind": {
+        "const": "releases",
+        "description": "Barcode resolved to releases.",
+        "type": "string"
+      },
+      "releases": {
+        "description": "Releases carrying this barcode (ranked).",
+        "items": {
+          "additionalProperties": false,
+          "description": "A release carrying the looked-up barcode.",
+          "properties": {
+            "artistCredit": {
+              "description": "Credited artist string.",
+              "type": "string"
+            },
+            "country": {
+              "description": "Release country code. Omitted when absent.",
+              "type": "string"
+            },
+            "date": {
+              "description": "Release date. Omitted when absent.",
+              "type": "string"
+            },
+            "mbid": {
+              "description": "Release MBID — chain to musicbrainz_get_release.",
+              "type": "string"
+            },
+            "score": {
+              "description": "Lucene relevance score, 0–100 (barcode is a search filter; exact = 100).",
+              "type": "number"
+            },
+            "title": {
+              "description": "Release title.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "mbid",
+            "title",
+            "artistCredit",
+            "score"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "kind",
+      "identifier",
+      "releases"
+    ],
+    "type": "object"
+  }
+]

10 tool updatesJun 16, 2026
- First observedmusicbrainz_browse_entities
- First observedmusicbrainz_get_artist
- First observedmusicbrainz_get_cover_art
- First observedmusicbrainz_get_label
- First observedmusicbrainz_get_recording
- First observedmusicbrainz_get_release
- First observedmusicbrainz_get_release_group
- First observedmusicbrainz_get_work
- First observedmusicbrainz_lookup_identifier
- First observedmusicbrainz_search_entities

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity – fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

musicurainz A
io.github.pipeworx-io
MusicBrainz MCP — wraps MusicBrainz Web Service v2 (free, no auth)
Art & Culture Search Entertainment & Media
352
openlibrary-mcp-server A
io.github.cyanheads
Search books and authors, fetch editions, browse subjects, and resolve cover images.
Search Education & Learning Tools Open Data
1023
wikidata-mcp-server A
io.github.cyanheads
Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers.
Knowledge & Memory Search Open Data
723
Last Fm B
io.github.pipeworx-io
Last.fm artist/album/track metadata (free API key required)
Entertainment & Media Search
402

Related MCP Servers

mcp-musicbrainz
Search Open Data Entertainment & Media
pipeworx-io
A
license
Not graded
quality
C
maintenance
Enables searching music artists and releases, and retrieving artist biographies, discographies, release track listings, credits, and metadata through the MusicBrainz API.
Updated 14 days ago (2026-08-26 17:23 UTC)
2
MIT
MusicBrainz MCP Server
Search Art & Culture Entertainment & Media
zas
A
license
A
quality
D
maintenance
Enables AI assistants to query the MusicBrainz music database for artists, albums, recordings, and labels. It provides tools for advanced searches, detailed metadata retrieval, and accessing cover art information.
Updated 5 months ago (2026-04-05 09:55 UTC)
17
12
GPL 3.0
musicbrainz-mcp
Entertainment & Media Art & Culture
chrischall
A
license
A
quality
A
maintenance
An MCP server that provides live access to MusicBrainz metadata and Cover Art Archive images, with optional OAuth-based submission of tags, ratings, and collection edits.
Updated 13 hours ago (2026-09-08 19:26 UTC)
9
413
MIT
music-mcp-agent
thelma-tertrais
F
license
Not graded
quality
C
maintenance
Enables music search, metadata retrieval, local audio analysis (tempo, key, energy), recommendations, song recognition, and classical work resolution via Spotify, Last.fm, AudD, MusicBrainz, and Songkick APIs.
Updated 2 months ago (2026-07-17 23:27 UTC)
-

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.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Frequently Asked Questions

Discussions

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources