Fetch one page of NDTV's video feed to retrieve metadata for recent clips by page number; results exclude media bytes and player URLs.
Get NDTV latest videos. Returns one page from NDTV's separate latest-videos feed. This feed is not a category slug; use page sequentially. Results contain metadata only, with no media bytes or player URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based latest-video page |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full disclosure burden and does useful work: it warns the agent that results are metadata only and contain no media bytes or player URLs, which prevents a wrong assumption about the payload. It omits auth/permission needs and rate-limit behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences with no filler; the core action is front-loaded and each following sentence adds a distinct fact (feed identity, pagination, response shape).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description's note on metadata-only results is important and mostly compensates. For a trivial one-param list tool this is close to complete, with only auth/rate-limit context missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single parameter is already documented as a 1-based page. The description's 'use page sequentially' adds pagination semantics beyond the schema, but no format or bounds detail, so this sits at the baseline for a fully-documented schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Get NDTV latest videos') and clarifies the scope is one page from a dedicated latest-videos feed. It distinguishes itself from category-slug endpoints in the same family ('This feed is not a category slug'), though it doesn't name a specific sibling tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives actionable guidance: 'use page sequentially,' which tells the agent how to paginate rather than guess. It clarifies the feed type so the agent knows this is not a category-browsing call, but it doesn't state explicit when-not-to-use or name an alternative tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.