ntv-mcp

ntv_get_article

Retrieve the full text of a single n-tv.de article from its URL for reading or analysis. Use it when you need article content beyond headlines or summaries.

Instructions

Full text of one n-tv article. url: an n-tv.de article link, e.g. https://www.n-tv.de/politik/...-id31518724.html (video pages may return little or no body text).

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

Input Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

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 full behavioral burden. It does disclose a genuinely useful trait: video pages may return little or no body text, which sets expectations about empty-ish results, but it says nothing about failure modes (invalid/non-article URLs), redirects, paywalls, or rate limits.

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?

One short sentence plus a single parenthetical caveat, with the core purpose front-loaded. Nothing is padded; even the awkward line break doesn't obscure meaning.

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?

A single-parameter extractor with an output schema, so return values need no explanation. Input shape and the main quality caveat are covered; only error behavior for invalid or non-article URLs is left unstated.

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% (a bare 'url' string), so the description must compensate, and it does: it specifies an n-tv.de article link and gives a concrete example pattern including the -id<number>.html form. It does not say what happens with non-article or off-domain URLs.

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 concrete verb+resource: 'Full text of one n-tv article', which is specific and scoped to a single article. It contrasts with list-style siblings like ntv_headlines or ntv_search_news implicitly, but never names a sibling or explicitly routes between them.

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 url format tells the agent which input to supply, and the parenthetical warns that video pages may yield little body text. There is no explicit when-to-use/when-not guidance, e.g. that this should be called only after obtaining a link from headlines or search.

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

Deploy Server