Skip to main content
Glama
qobuz-mcp
by cheubes

Search Catalog

search_catalog
Read-only

Search the Qobuz catalog for albums, artists, tracks, or playlists to get their IDs and public URLs for use with other Qobuz tools.

Instructions

Search the Qobuz catalog for albums, artists, tracks or playlists.

Returns one page of items of the requested type, with their Qobuz IDs and public URLs. Use the IDs with the other tools, for example get_album for an album.

Tool call template

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

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "type": "<type>"
    },
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesKind of items to search for.
limitNoNumber of items to return, 1 to 100.
queryYesFree-text search, as on Qobuz.
offsetNoNumber of items to skip, to fetch next pages.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the paginated shape of the response ("Returns one page") and that results carry Qobuz IDs and public URLs, which is exactly the information needed to chain into follow-up calls.

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?

Three short sentences with the purpose front-loaded and no filler. The final sentence about using IDs is slightly redundant with the preceding sentence about returned IDs, a minor overlap but not wasteful enough to penalize heavily.

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

Completeness4/5

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

For a read-only search tool with an output schema, full parameter descriptions, and clear annotations, the description covers purpose, response shape, and the follow-up workflow. Rate limits and how to continue paging across multiple calls are not addressed, though offset is documented in the schema, leaving only a small gap.

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%, with the enum, limit bounds, and offset meaning all documented in the schema itself. The description's phrase "one page" loosely reinforces the limit/offset paging model but adds no syntax, format, or edge-case guidance beyond the schema, so the baseline of 3 applies.

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

Purpose4/5

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

The description gives a specific verb and resource ("Search the Qobuz catalog") and enumerates the four item types covered, which lets an agent distinguish this from the family of single-item retrieval tools like get_album and get_artist. It stops short of explicitly separating itself from sibling search tools such as search_stories, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The description names a downstream use ("Use the IDs with the other tools, for example `get_album` for an album"), which tells the agent what to do after searching. It offers no when-to-use or when-not-to-use criteria, no prerequisites, and no explicit alternative search path, so usage is only implied.

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