Skip to main content
Glama
qobuz-mcp
by cheubes

Search Stories

search_stories
Read-only

Search Qobuz magazine stories for news, interviews, and reviews by free-text query, returning titles, summaries, authors, dates, sections, and links to read them.

Instructions

Search Qobuz magazine stories: news, interviews, reviews.

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": {
      "query": "<query>"
    },
    "name": "search_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return, 1 to 100.
queryYesFree-text search in the magazine.
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

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 the safety profile is covered; the description adds real behavioral information on top by listing the returned fields (title, summary, authors, date, sections, link) and explicitly warning that full text is not available. That 'no full text' caveat is exactly the kind of limitation an agent cannot get from annotations or 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 sentences, no filler, with the core purpose front-loaded and the return-shape/limitation details following. Every clause carries information an agent would otherwise lack.

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 present, return values are already structured, yet the description still usefully previews them and flags the full-text limitation. The only meaningful gap is sibling routing, which keeps it from being fully complete for a search tool in a large catalog.

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 each parameter (query, limit, offset) carries its own description, so the schema does the work. The description contributes no additional meaning about query syntax, matching behavior, or pagination semantics, leaving it at the baseline.

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?

Names a specific verb+resource ('Search Qobuz magazine stories') and enumerates the content types covered (news, interviews, reviews), so an agent knows exactly what corpus is being searched. It does not, however, distinguish itself from plausible siblings such as search_catalog or list_related_stories.

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 noun phrase 'magazine stories' — an agent can infer this is the route for editorial content rather than catalog items. There is no explicit when-to-use, when-not-to-use, or named alternative anywhere in the description.

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