Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ndtv_live_blogs

Fetch NDTV live-blog index pages: retrieve public www.ndtv.com live-blog cards and request sequential pages until upstream returns not found.

Instructions

Get NDTV live-blog index. Returns one page of public NDTV live-blog cards. Pages include only www.ndtv.com live blogs; sister-site cards are excluded. NDTV does not expose a total count or continuation marker; request sequential pages until the upstream reports not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based index page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does well: it discloses filtering behavior (only www.ndtv.com cards, sister-site cards excluded) and a critical pagination quirk (no total count or continuation marker; paginate until not found). It does not mention rate limits or auth, but for a public read listing these are minor.

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?

Front-loaded with the primary action, then return shape, then constraints. Three tight sentences with little waste, though the sister-site exclusion and pagination notes could be marginally condensed.

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 simple one-parameter listing tool with no output schema, the description covers purpose, return shape, filtering, and pagination termination. An agent has what it needs to call it correctly; only auth/rate details are absent.

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 coverage is 100% and the single page parameter is already documented as "1-based index page." The description adds the pagination context (sequential pages, no continuation marker) but does not extend the meaning of the parameter itself, so the baseline 3 is appropriate.

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+resource ("Get NDTV live-blog index") and clarifies the return unit (one page of public live-blog cards). It is distinguishable from the singular ndtv_live_blog sibling as the listing/index tool, though it does not name that sibling explicitly to route the agent.

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 implied by "index" and the pagination instruction, but there is no explicit when-to-use vs. the ndtv_live_blog detail tool or when-not guidance. The agent must infer that this is the entry-point pagination tool rather than a specific-blog viewer.

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