ntv-mcp

ntv_videos

Retrieve recent n-tv videos by setting a result limit to browse available news clips.

Instructions

Latest n-tv videos. 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": "ntv_videos"
  }
}

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.0Nov 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It adds a useful constraint range (1..50) but says nothing about what 'latest' means in time or count, ordering, or whether results are paginated or refreshed; the presence of an output schema covers return shape but not these semantics.

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 compact sentences with the purpose front-loaded and the parameter constraint immediately after; nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter list tool with an output schema, the definition covers purpose and parameter bounds adequately. It leaves open what 'latest' implies (time window, ordering) and whether there is a maximum item count or pagination, which an agent would need for correct use.

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?

With 0% schema description coverage, the schema exposes only a default of 10 and no bounds. The description supplies the missing semantics by giving the valid range 1..50 and restating the default, which is genuine added meaning beyond the structured field.

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 specific resource ('n-tv videos') and a freshness qualifier ('Latest'), so an agent can distinguish it from ntv_get_article or ntv_markets by content type. It stops short of stating an explicit retrieval verb or contrasting itself with the sibling video/news tools, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over ntv_headlines, ntv_search_news, or ntv_get_article. The only implied usage is 'get recent videos', which the name already conveys.

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

Deploy Server