Skip to main content
Glama
qobuz-mcp
by cheubes

List New Releases From Favorites

list_new_releases_from_favorites
Read-only

Retrieve recent releases from favorite artists, labels, or awards to find new music based on your Qobuz favorites.

Instructions

List recent releases from the user's favorite artists, labels or awards.

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": {
      "source": "<source>"
    },
    "name": "list_new_releases_from_favorites"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
sourceYesWhose new releases: the user's favorite artists, labels or awards.
genre_idNoOnly releases of this genre (an ID from `list_genres`).

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds only the notion of 'recent', which it never defines (how recent, in what order), and says nothing about pagination behavior or what the open-world lookup actually queries.

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?

A single efficient sentence with no waste and the key scope up front. It is lean to the point of under-specification rather than being padded.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the parameters are fully documented in schema. What is missing is a definition of 'recent' and any hint about ordering or result window, which matter for a feed-style listing 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?

Schema description coverage is 100%; the enum, limit, offset and genre_id are all documented in the schema. The description merely echoes the source enum values and adds no meaning beyond it.

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?

States a specific verb+resource ('List recent releases') and scopes the source to favorite artists, labels or awards. It does not distinguish itself from siblings like list_favorites or list_featured_albums, so it falls short 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent cannot tell from the description why it would pick this over list_favorites or search_catalog.

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