mediathek-mcp

mediathek_by_topic

Retrieve all episodes of a German TV show or series by topic, sorted newest first, with an optional limit to control the number of results.

Instructions

All episodes of one show/series (topic), newest first. topic: e.g. "heute journal" or "Tagesschau". limit: 1..50 (default 10).

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": {
      "topic": "<topic>"
    },
    "name": "mediathek_by_topic"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`topic`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: results are ordered newest first and limit is bounded to 1..50. It says nothing about what happens on an unrecognized topic (empty result vs error), whether topic matching is exact or fuzzy, or pagination beyond the limit cap.

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?

Two short sentences, behavior front-loaded, and each parameter annotated inline. The telegraphic style ('topic:', 'limit:') is efficient, though it reads as notes rather than prose and omits a connecting statement about how topic and limit interact.

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 two-parameter lookup with an output schema that documents return values, the description covers the essentials: what is returned, ordering, and both parameter constraints. The remaining unknown is topic-matching behavior on miss or partial input, a minor gap at this complexity level.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it largely does: it gives concrete topic examples ("heute journal", "Tagesschau") and states the limit range and default (1..50, default 10). The only gap is whether topic must match a canonical show name exactly or is matched loosely.

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 resource and scope: 'All episodes of one show/series (topic), newest first.' The verb is implied by 'All episodes ... newest first' but the retrieval action and ordering are unambiguous. It does not explicitly distinguish itself from siblings like mediathek_search_programmes or mediathek_programme_detail, though the 'one show/series' framing hints at exact-topic enumeration.

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 implied rather than stated: an agent can infer this is the tool for pulling a single show's episode list rather than searching across shows. There is no explicit when-not guidance, no mention of prerequisites, and no named alternative for fuzzy or cross-show lookups, leaving the choice against mediathek_search_programmes to inference.

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

Deploy Server