Skip to main content
Glama
tagesschau-mcp

tagesschau-mcp

tagesschau_latest_videos

Retrieve current tagesschau.de videos, newest first, with an optional 1–50 result limit.

Instructions

Latest tagesschau.de videos ("Aktuelle Videos"), 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": "tagesschau_latest_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose two useful behaviors: results are ordered newest first, and the limit is bounded to 1..50. It says nothing about authentication, rate limits, or whether the feed is cached/limited in window, and it does not describe what a video entry holds — though the output schema covers return shape.

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 short sentences with zero filler; the resource and ordering are front-loaded and the parameter constraint follows. Nothing is redundant given the structured fields.

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 one-parameter read tool with an output schema, the description covers purpose, ordering, and the parameter bounds adequately. It omits whether more than 50 items can be retrieved at all (no offset/pagination parameter is mentioned), which is the only notable gap.

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 coverage is 0% and the schema only declares an integer with default 10, so the description genuinely adds value by giving the valid range 1..50 and restating the default. That fully defines the single parameter's semantics beyond the schema.

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 resource (latest tagesschau.de videos / "Aktuelle Videos") and its ordering (newest first), which an agent can distinguish from news, headline, and article siblings. It stops short of explicitly contrasting with those siblings, so it is clear but not maximally differentiating.

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: the word "Latest" plus "newest first" signals a browse-recent-content tool, but there is no statement of when to prefer it over tagesschau_headlines or tagesschau_news_by_section, and no exclusions or prerequisites.

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