Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ndtv_author

Fetch an NDTV author or agency profile and paginated authored news stories from a canonical URL. Request pages sequentially until the articles list is empty.

Instructions

Get an NDTV author profile. Returns an NDTV author's or news agency's byline profile (name, role, biography, image) and one page of authored news stories from a canonical author URL. Request sequential pages until articles is empty; NDTV does not expose a total count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical NDTV author or agency URL
pageNo1-based authored news story page; request sequentially until articles is empty

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.9
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-based authored news story page; request sequentially until articles is empty",
+  "type": "integer"
+}
  2. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose non-obvious behavior: the response bundles profile metadata plus one page of stories, pages are sequential, and NDTV exposes no total count. It omits auth/rate-limit expectations, but the pagination semantics are the meaningful behavioral disclosure here.

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 tightly front-loaded sentences with no filler: the first states the action, the second enumerates returns and strictly necessary pagination guidance. Nothing could be cut without losing information.

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?

There is no output schema, and the description compensates by naming the profile fields and explaining pagination termination, which is what an agent needs to call it correctly. It stops short of covering failure modes or URL sourcing, but is adequate for a two-parameter read tool.

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%, so both parameters are already documented (canonical author URL; 1-based page). The description restates 'canonical author URL' and the page-until-empty rule without adding syntax or format 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 an NDTV author profile') and details the returned payload (name, role, biography, image, plus a page of authored stories). However, it never names a sibling tool (e.g. ndtv_article or ndtv_search) to differentiate itself, leaving the agent to infer the boundary.

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?

Provides clear operational guidance for pagination ('request sequential pages until articles is empty'), but gives no when-to-use context versus alternatives or prerequisites beyond the canonical-URL input. Usage is implied by the pagination instruction rather than explicitly framed.

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