Skip to main content
Glama
qobuz-mcp
by cheubes

List My Playlists

list_my_playlists
Read-only

Lists playlists you own or follow in Qobuz, letting you filter by owned/followed and paginate through results to browse your library.

Instructions

List the playlists the user owns or follows.

Only playlists the user owns can be changed by the write tools.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
filterNoOnly playlists the user owns, or only those they follow. Omit for both.
offsetNoNumber of items to skip, to fetch next pages.

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 a non-obvious cross-tool behavioral fact — that write tools can only mutate owned (not followed) playlists — which materially affects how an agent interprets results. Pagination behavior is left to the schema.

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?

Two short sentences, zero redundancy, and the primary purpose is front-loaded before the secondary constraint. Every sentence carries information an agent needs.

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 an output schema, full parameter documentation, and read-only annotations, the description covers what remains: purpose, scope, and the owned-vs-followed mutability caveat. Only minor gaps such as pagination expectations are unaddressed, and the offset/limit schema largely covers those.

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 limit, filter, and offset fully documented in the schema itself, including the 'omit for both' default for filter. The description echoes the owned/followed distinction but adds no syntax or format detail beyond the schema, 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?

States a specific verb and resource with scope: 'List the playlists the user owns or follows.' That scope alone separates it from siblings like list_artist_playlists or list_featured_playlists, which return other parties' playlists. No sibling is named explicitly, so it stops 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 Guidelines4/5

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

The second sentence gives actionable routing context: if the intent is to modify a playlist, only owned ones qualify, which implies filtering to 'owned' before calling write tools. It does not explicitly address when to choose a sibling listing tool instead, so it is clear context rather than full when/when-not guidance.

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