Skip to main content
Glama
chrischall

musicbrainz-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search MusicBrainz

musicbrainz_search
Read-onlyIdempotent

Find MusicBrainz entities by plain-text name or fielded Lucene query; get ranked matches with MBIDs for artists, releases, recordings, and more.

Instructions

Search a MusicBrainz entity type with a Lucene query and get back ranked matches with their MBIDs. Plain text matches the entity name; fielded Lucene also works, e.g. artist:"Miles Davis" AND country:US, release:"Kind of Blue" AND format:Vinyl, or recording:"So What" AND dur:[540000 TO 560000]. Feed a returned MBID into musicbrainz_lookup for full detail. Read-only. Data from MusicBrainz (https://musicbrainz.org), the open music encyclopedia.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns MusicBrainz's payload untouched. No field projection: this server has no verified record of which MusicBrainz fields matter, and inventing one would risk dropping a field a caller needs.
limitNoMax results (1–100, default 25)
queryYesLucene query string (plain text or fielded)
entityYesEntity type to search
offsetNoResult offset for paging (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns MusicBrainz's payload untouched. No field projection: this server has no verified record of which MusicBrainz fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.2.2

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, and the description reinforces 'Read-only.' Beyond the annotations, it adds useful behavioral context: results are 'ranked matches with their MBIDs,' plain text matches entity names, and fielded Lucene queries are supported with concrete examples. It does not discuss rate limits or response shape details, but the safety profile is already covered by 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 compact, front-loaded with the core purpose, and every sentence earns its place: purpose, query semantics with concrete examples, and chaining to lookup. The read-only and data-source notes are brief and non-redundant enough to not feel wasteful.

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 search tool with 100% parameter schema coverage and strong annotations, the description is complete. It explains what results contain (ranked matches with MBIDs), how to execute both plain-text and Lucene queries, and where to send the resulting MBID next. The absence of an output schema is mitigated by the explicit mention of MBIDs and the routing to lookup for full detail.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds real value above the schema by showing query syntax examples such as `artist:"Miles Davis" AND country:US`, `release:"Kind of Blue" AND format:Vinyl`, and `recording:"So What" AND dur:[540000 TO 560000]`, plus noting that plain text matches the entity name. This helps an agent construct valid queries more confidently.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Search a MusicBrainz entity type with a Lucene query and get back ranked matches with their MBIDs.' It clearly distinguishes this from lookup by saying 'Feed a returned MBID into musicbrainz_lookup for full detail.' The scope is precise and leaves no doubt about what the tool does.

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 clearly frames when to use this tool: when you need to find entities by Lucene text or fielded queries. It also provides chaining guidance to musicbrainz_lookup, but it does not explicitly name exclusions for browse or resolve, so it stops short of fully enumerating alternatives.

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

Deploy Server

Other Tools