Skip to main content
Glama
qobuz-mcp
by cheubes

Add Favorites

add_favorites

Add albums, artists, or tracks to a Qobuz user's favorites in one request, so you can save multiple media items without separate calls.

Instructions

Add albums, artists and/or tracks to the user's favorites, in one call.

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": "add_favorites"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idsNo
track_idsNo
artist_idsNo

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description adds that favorites belong to "the user" (implicitly the authenticated user) and that mixed entity types can be combined in a single call. It does not disclose idempotency (what happens on duplicate favorites), partial-failure behavior, or any rate/permission constraints beyond what the annotations say.

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 short sentence, verb-first and front-loaded with the resource and the batching benefit; nothing is redundant. It is efficient but too thin to earn top marks.

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?

Annotations and an output schema are supplied, lowering the description's burden, so a 3 is defensible for a simple 3-parameter mutation. Still, with all parameters optional and 0% top-level schema coverage, the description should say at least one ID list is needed and whether duplicates are tolerated.

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

Parameters2/5

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

Schema description coverage is reported at 0% for the top-level properties, so the description must compensate — it only restates the three entity types (albums, artists, tracks) without conveying the ID formats (album IDs are strings, track/artist IDs are integers) or that every parameter is optional/nullable and at least one should presumably be supplied. This leaves the agent to open the schema to call the tool correctly.

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 ("Add ... to the user's favorites") and names the three entity types, which makes it clearly distinct from the sibling remove_favorites by the verb 'Add'. It does not explicitly name or defer to that sibling, keeping it just 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 Guidelines3/5

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

The phrase "in one call" implies a batching use case — you don't need separate calls per entity type — but there is no explicit when-to-use/when-not guidance, no mention of remove_favorites for the inverse operation, and no note about prerequisites such as being authenticated as the user.

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