Skip to main content
Glama
qobuz-mcp
by cheubes

List Purchases

list_purchases
Read-only

Retrieve albums or tracks a user has purchased on Qobuz, with limit and offset controls for paging through results.

Instructions

List the albums or tracks the user has purchased on Qobuz.

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_purchases"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesKind of purchases 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.6/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, and the description is consistent with them. The description adds essentially no behavioral context beyond the annotations — nothing about result ordering, whether purchases are paginated server-side, or how purchases differ from favorites; the output schema and the limit/offset parameters carry the rest.

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?

A single sentence with no filler, front-loading the verb and resource. Every word earns its place and there is no redundant restatement of the title.

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 simple read-only paginated list with an output schema, full parameter documentation, and annotations covering the safety profile, the description is adequate — an agent knows what it returns and how to page it from the schema. A brief note on how purchases relate to favorites would have closed the remaining 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%, and the schema documents the type enum, the 1–100 limit range, and the offset paging semantics, so the schema does the heavy lifting. The description's 'albums or tracks' merely echoes the existing enum values rather than adding meaning, which lands at the baseline for full schema coverage.

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 albums or tracks the user has purchased on Qobuz') and scopes it to the user's own purchases, which separates it from catalog-wide siblings like search_catalog. It stops short of naming or distinguishing it from the closest overlapping sibling, list_favorites, so an agent must still infer the purchases-vs-favorites boundary.

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 phrase 'the user has purchased' — an agent can infer this is the tool for purchase history rather than wishlists or the general library. There is no explicit statement of when to prefer this over list_favorites or check_library, and no exclusions or prerequisites are given.

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