Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ndtv_live_blog

Retrieve structured metadata and ordered updates from an NDTV live blog using its canonical article URL; regular article URLs are rejected with an error.

Instructions

Get structured updates from an NDTV live blog. Returns the metadata and ordered updates of an NDTV live blog, given its canonical article url. The blog carries title, description, section, authors, image and publish and update times. Each update has its title, URL, body text, timestamps, authors and image when NDTV gives them. A regular article URL is rejected with an error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical NDTV live-blog article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.3/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. It discloses a rich behavioral profile: metadata fields, ordered updates, per-update fields, and error behavior for non-live-blog URLs. It omits auth requirements and rate limits, but for a read-only retrieval tool this is solid coverage.

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?

Four sentences, front-loaded with purpose and input, then return structure, then the rejection rule. Nothing is wasted, though the field enumeration is slightly list-heavy.

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?

No output schema exists, so the description must describe returns, and it does so thoroughly (blog-level fields and per-update fields). For a single-parameter read tool this is near-complete; only auth/error-edge specifics are absent.

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 100% for the single url parameter, so baseline is 3. The description adds meaning beyond the schema by specifying 'canonical article url', tying it to live blogs specifically, and warning that regular article URLs produce an error.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get structured updates') and resource ('NDTV live blog'), and explicitly distinguishes itself from regular article retrieval by noting that a regular article URL is rejected. An agent can tell this apart from ndtv_article without opening either schema.

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?

Clear context: use with a canonical live-blog article URL, and it explicitly states that regular article URLs are rejected with an error, effectively defining a when-not condition. It does not name the sibling tool to use for regular articles (e.g. ndtv_article), so it falls short of explicit alternative routing.

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