Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

timesofindia_headlines

Retrieve current Times of India headlines for a chosen section or city edition. Specify a section slug to get titles, URLs, summaries, authors, and publication times.

Instructions

Get The Times of India section headlines. Returns the current headlines for one Times of India section or city edition. section is required, for example top-stories, india, world, business, cricket, mumbai, delhi or bangalore. Items carry the title and URL, plus summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesTimes of India section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/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 does disclose the return shape well (title, URL, plus summary/author/time/image 'when the outlet provides them'), but says nothing about pagination, freshness/caching, or rate limits for a read operation.

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 core purpose and followed by the required-parameter constraint and return contents. No filler, though the final sentence about item fields could be trimmed.

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?

With no output schema and no annotations, the description covers the essentials an agent needs: what it returns, that section is required, and example values. Missing only pagination/volume expectations and sibling routing, which are minor for a simple one-param read.

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 enum fully enumerates valid slugs, so the schema already documents the parameter. The description adds marginal value by illustrating representative values and framing them as sections vs city editions, but no format or selection guidance beyond the enum.

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 The Times of India section headlines') and scopes it to one section or city edition. It is clearly distinguishable from timesofindia_article/news in intent, but never explicitly names or contrasts those siblings.

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?

The description implies usage ('for one Times of India section or city edition') and lists example section slugs, but gives no explicit when-to-use vs alternatives such as timesofindia_news or timesofindia_sections, and no prerequisites.

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