Skip to main content
Glama
qobuz-mcp
by cheubes

List Favorites

list_favorites
Read-only

List a user's favorite albums, artists, or tracks newest first, including the date each item was added to favorites.

Instructions

List the user's favorite albums, artists or tracks, newest first.

Each item comes with favorited_at, the date it was added to the favorites.

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": {
      "type": "<type>"
    },
    "name": "list_favorites"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesKind of favorites to list.
limitNoNumber of items to return, 1 to 100.
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.5/5.0
Behavior3/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 two useful facts beyond that: results are ordered newest-first and each item carries a `favorited_at` timestamp. It stops short of describing pagination limits, total-count behavior, or empty-library 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?

Two short sentences, front-loaded with the action and scope. The second sentence about `favorited_at` is somewhat redundant given an output schema exists, but it is genuinely useful context for a caller deciding whether this tool answers their question.

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?

With full schema coverage, an output schema, and annotations covering read-only/open-world semantics, the remaining description burden is small. Ordering and the presence of a timestamp are stated; only minor details like total result counts or pagination termination are absent.

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 `type` enumerated and `limit`/`offset` fully documented including bounds and defaults. The description adds no parameter-level detail (e.g., default page size or how offset interacts with ordering), so the baseline 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 ('List the user's favorite albums, artists or tracks') plus the sort order ('newest first'), so the operation is unambiguous. It does not name or contrast with siblings such as list_new_releases_from_favorites, but the 'list favorites' framing is distinct enough on its own.

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?

Usage is only implied by the verb 'list' and the 'favorite' qualifier; the reader can infer this is the read counterpart to add_favorites/remove_favorites. There is no explicit when-to-use or when-not guidance, and no mention of pagination strategy for retrieving large favorite sets.

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