mediathek-mcp

mediathek_search_programmes

Search German Mediathek programmes by title, topic, or description, with optional channel filtering, to find relevant broadcasts and listings.

Instructions

Search Mediathek programmes by title, topic or description. query: free text, e.g. "Tagesschau" or "Tatort". channel: optional, e.g. "ZDF" (see mediathek_list_channels). 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": {
      "query": "<query>"
    },
    "name": "mediathek_search_programmes"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`channel`	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 makes clear this is a free-text lookup and gives the limit range, but says nothing about match semantics (substring vs. fuzzy), result ordering, or what happens if limit exceeds 50. With an output schema present, return-value description is correctly omitted, keeping this at an adequate rather than rich level.

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?

The purpose sentence is front-loaded and each subsequent clause covers exactly one parameter with an example, so nothing is wasted. The colon-separated parameter listing is terse but readable; a slight polish would separate these into a short line each.

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 three-parameter search tool with an output schema, this covers the essentials: what is searched, valid channel sourcing, and the limit bound. The only meaningful gaps are result ranking/pagination semantics and the behavior of an over-range limit, which are minor for this complexity.

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 largely does: query is explained with concrete examples ('Tagesschau', 'Tatort'), channel is marked optional with an example and a pointer to the channel listing tool, and limit is bounded to 1..50 with default 10. Only the matching behavior of query and the error case for out-of-range limits remain unexplained.

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 ('Search Mediathek programmes') and names the three fields searched (title, topic, description), which is more than the name alone conveys. It does not explicitly distinguish itself from siblings like mediathek_by_channel or mediathek_by_topic, though the channel hint implies the relationship.

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: it explains that channel is optional and directs the agent to mediathek_list_channels for valid values, which is a useful routing hint. However, there is no explicit guidance on when to prefer this free-text search over the sibling tools that filter by channel or topic.

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

Deploy Server