Skip to main content
Glama
qobuz-mcp
by cheubes

List Related Stories

list_related_stories
Read-only

Retrieve Qobuz magazine stories for an album, artist, label, playlist, or award, returning titles, summaries, authors, dates, sections, and links; full text is not included.

Instructions

List Qobuz magazine stories about an album, an artist, a label, a playlist or an award.

Each story comes with its title, summary, authors, date and sections, and a link to read it on Qobuz. The full text is not available.

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": {
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>"
    },
    "name": "list_related_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
offsetNoNumber of items to skip, to fetch next pages.
entity_idYesQobuz ID of that item: an album ID, or another ID in digits.
entity_typeYesWhat the stories are about.

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
has_moreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and reach are covered; the description adds genuinely new behavioral facts by stating the payload shape (title, summary, authors, date, sections, link) and, importantly, that full story text is unavailable. That limitation prevents an agent from promising content it cannot retrieve. It says nothing about pagination behavior or result caps beyond what the schema fields imply.

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?

Three short sentences, front-loaded with the action and scope, then the payload, then the limitation. The middle sentence partially duplicates what the output schema already declares, costing a little density, but there is no filler or hedging.

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

Completeness5/5

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

With an output schema present, the return values need not be spelled out, and annotations carry the read-only/open-world profile; the description covers the remaining gap an agent would actually trip on, namely that story bodies are not retrievable. Nothing essential for a correct call appears to be missing.

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 all four parameters are documented inline, including the enum for entity_type and the ID pattern, so the baseline is 3. The description's enumeration of entity types merely restates the enum rather than adding meaning such as ID formats or how limit/offset interact with total story counts.

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 ('List Qobuz magazine stories') and scopes it to the entity types an agent can query, which is far more informative than the title alone. It does not name the obvious sibling 'search_stories' or explain how this differs from keyword-based story search, so differentiation is left implicit.

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 phrasing 'stories about an album, an artist, a label...' implies usage: call this when you have a specific entity and want editorial content attached to it. There is no explicit when-not guidance or pointer to an alternative tool for free-text story discovery, so the agent must infer the boundary from sibling names.

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