Skip to main content
Glama
qobuz-mcp
by cheubes

List Genres

list_genres
Read-only

Browse Qobuz genres one level at a time and retrieve genre IDs to filter featured albums and playlists. Omit the parent genre ID for top-level genres or provide one to list subgenres.

Instructions

List Qobuz genres, one level of the tree at a time.

Each genre's path holds its ancestor genre IDs, from the root to its direct parent. Genre IDs filter list_featured_albums and list_featured_playlists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_genres"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
parent_genre_idNoList the sub-genres of this genre. Omit for top-level genres.

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavior beyond that: results are a single tree level, and each item carries an ancestor `path` from root to direct parent. It says nothing about result volume or paging, though the schema and output schema cover that.

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?

Three short sentences, front-loaded with the core action and scope, then output shape, then downstream use. Nothing is redundant and each sentence carries unique information.

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 a simple read-only listing tool with full schema coverage, existing annotations, and an output schema, the description covers purpose, traversal model, and downstream integration well. Only minor items such as expected result size or total-count behavior are absent, which the output schema likely handles.

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 `parent_genre_id`, `limit`, and `offset` all documented inline, including the schema's own note to omit `parent_genre_id` for top-level genres. The description reinforces the tree-level concept but adds no syntax or format detail 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 opens with a specific verb and resource ("List Qobuz genres") and immediately scopes the operation ("one level of the tree at a time"), so an agent knows exactly what it retrieves. There is no sibling that lists genres, so explicit differentiation is unnecessary, which keeps this just shy of a 5.

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 gives clear operational context: call it level by level using `parent_genre_id`, and the returned genre IDs are intended to feed `list_featured_albums` and `list_featured_playlists`. It does not state when-not to use it or name a competing tool, but the workflow guidance is explicit enough to route the agent correctly.

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