Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indiatoday_headlines

Fetch India Today headlines for a chosen section slug, returning 12-60 text stories with title, URL, type, summary, and image. Use valid slugs like top-news or cricket.

Instructions

Get India Today section headlines. Returns the text stories listed on one India Today section page, typically 12 to 60. section is required and takes one of 35 slugs such as top-news, cricket, markets, bollywood or fact-check; other values return 400. Items have title, URL, type, summary and image when shown, but no published_at.

Input Schema

NameRequiredDescriptionDefault
sectionYesIndia Today section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 full burden and largely meets it: it discloses the item count range (12–60), the returned fields, the notable absence of published_at, and the 400 error on invalid sections. It doesn't explicitly state it is a read-only operation, keeping it from a 5.

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 the purpose and then the constraints and return shape. No filler, though it is dense enough that a small amount of structure could help readability.

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 compensates well by describing returned fields and the item-count range. Combined with the schema's full enum coverage and the documented error behavior, an agent has nearly everything needed to call it correctly.

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% and the enum lists all 35 slugs, so the baseline is 3. The description adds meaning beyond the schema by noting the count (35 slugs), giving examples, and documenting the 400 response for out-of-enum values.

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 India Today section headlines') and clarifies the scope as 'one India Today section page'. It does not explicitly name or differentiate from siblings like indiatoday_news or indiatoday_sections, so it stops short of a 5.

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?

It makes the required/constrained usage clear ('section is required', valid slugs, other values return 400), but gives no explicit when-to-use guidance versus the sibling news/article/sections tools. Usage is implied rather than routed.

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