mediathek-mcp

mediathek_latest_broadcasts

Fetch recent programmes across all German Mediathek channels in reverse chronological order, with a configurable result limit from 1 to 50.

Instructions

Newest programmes across all channels, newest first. limit: 1..50 (default 10).

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": "mediathek_latest_broadcasts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

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?

No annotations are supplied, so the description carries the full burden; it discloses the sort order ('newest first') and the limit range, which are genuine behavioral facts. It says nothing about whether this is a read-only listing, how results are truncated, or whether older items are reachable at all via limit alone.

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 terse sentences, front-loaded with scope and ordering before the parameter constraint. Nothing is padded and no sentence is redundant.

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 need not be described, and the sole parameter is documented with range and default. The remaining gap is discoverability of older content — with only a limit and no cursor/offset, an agent cannot tell whether this tool can reach anything beyond the newest N items.

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 coverage is 0% for the single 'limit' parameter, but the description compensates by giving the accepted range 1..50 and the default of 10, which the schema itself omits. It does not describe what an out-of-range value does or how limit interacts with the newest-first ordering, so the compensation is partial rather than complete.

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 names a concrete resource ('programmes across all channels') and a verb-like action ('newest ... newest first'), so an agent knows this returns an unfiltered newest-first listing. It does not explicitly contrast itself with mediathek_by_channel or mediathek_by_topic, but the 'across all channels' scope implies the distinction.

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 by 'across all channels' — i.e. use this when no channel or topic filter is wanted — but the description never states when to prefer a sibling such as mediathek_by_channel or mediathek_search_programmes. There are no exclusions or prerequisites, leaving the agent to infer routing.

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

Deploy Server