Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ndtv_videos

Fetch one page of NDTV category video metadata cards by category slug and page; discover supported categories first, then page sequentially.

Instructions

Get videos from an NDTV category. Returns one page of metadata cards from a supported NDTV-hosted video category. Use ndtv-video-categories to discover the complete supported category set; request pages sequentially. This returns no media bytes or player URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based category result page
categoryYesNDTV video category slug from ndtv-video-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the disclosure burden and does well: it states the return is 'one page of metadata cards' and explicitly that there are 'no media bytes or player URLs', preventing a common misassumption. It omits auth requirements, rate limits, and page-size behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with purpose, then the discovery prerequisite, then the negative-scope caveat. No filler, though the sequential-paging note is slightly buried mid-sentence.

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 two-parameter, no-output-schema, annotation-free listing tool, the description covers what the tool returns and what it does not, plus how to obtain valid categories. Missing pagination termination/limits and error behavior, but nothing critical to correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are already documented in the schema (including that category must come from ndtv-video-categories). The description adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 specific verb and resource ('Get videos from an NDTV category') and clarifies the shape of the result ('one page of metadata cards'), which separates it from the single-item ndtv_video sibling. It does not explicitly contrast itself with ndtv_latest_videos, so the category-scoped distinction is only implied by 'from an NDTV category'.

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?

Explicitly directs the agent to ndtv-video-categories to discover valid categories and instructs 'request pages sequentially', giving concrete operational context. It stops short of saying when to prefer this over ndtv_latest_videos or ndtv_video.

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

Deploy Server

Other Tools