Skip to main content
Glama
tagesschau-mcp

tagesschau-mcp

tagesschau_get_article

Retrieves the complete text and metadata of a tagesschau.de article from its URL, including headline, description, publish date, author, and full article body.

Instructions

Full text of one tagesschau.de article: headline, description, publish date, author and the complete article body. url: a tagesschau.de article link, e.g. from tagesschau_headlines.

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": {
      "url": "<url>"
    },
    "name": "tagesschau_get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the returned fields and their article-scoped nature. It says nothing about handling of invalid or non-article URLs, redirects, or retrieval failures, and only implicitly signals that this is a non-mutating fetch. Adequate but thin for a zero-annotation tool.

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?

Three compact clauses: what you get, then the field list, then the sole parameter with its source. The return contents are front-loaded and every sentence carries information used at call time.

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 fetch tool with an output schema covering return values, the description is nearly complete: purpose, returned fields, and valid input source are all stated. Only edge behavior on malformed/non-article URLs is absent, which is a minor gap at 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 coverage is 0% for the single 'url' parameter, so the description must define it — and it does: it is a tagesschau.de article link obtained e.g. from tagesschau_headlines. That specifies both the domain constraint and the provenance of the value, which meaningfully exceeds the bare 'string' schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete retrieval action plus the exact resource ('Full text of one tagesschau.de article') and enumerates what comes back: headline, description, publish date, author, and complete body. This clearly separates it from the listing tools like tagesschau_headlines, which the description implicitly contrasts by naming it as the URL source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'url: a tagesschau.de article link, e.g. from tagesschau_headlines' tells the agent where a valid input comes from, implying the two-step flow headlines → full article. It stops short of explicit when-not-to-use guidance (e.g. for section indexes or video pages), so the alternative-selection guidance is implied rather than stated.

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