Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

hindustantimes_headlines

Fetch current Hindustan Times section headlines by passing a required slug, returning titles, URLs, summaries, authors, publication times, and images.

Instructions

Get Hindustan Times section headlines. Returns current Hindustan Times headlines for one section. section is required and takes one of 24 slugs such as india-news, world-news, cricket, business, htcity or editorials. Each item has its title, URL, summary, author, publication time and image where the site provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesHindustan Times 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?

With no annotations, the description carries the full behavioral burden. It does usefully disclose the returned item shape (title, URL, summary, author, publication time, image) and honestly caveats 'where the site provides them,' but says nothing about result count, pagination, freshness window, or rate limits for a live news endpoint.

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 sentences, front-loaded with the purpose, then the parameter requirement, then the return shape. Tight and readable; the enum example list is slightly redundant but not wasteful.

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 compensates well by describing the returned fields and their optionality. It is nearly complete for a single-parameter read tool, though it leaves pagination and result volume unspecified.

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 description coverage is 100% and the enum already lists all 24 slugs, so the schema does the heavy lifting. The description adds only marginal value by restating that section is required and giving a few examples ('india-news', 'cricket', 'htcity'), which the enum already provides verbatim.

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 Hindustan Times section headlines' -- and clarifies the scope as 'for one section.' This clearly separates it from a generic news feed, but it never names the closely related siblings (hindustantimes_news, hindustantimes_sections, hindustantimes_article) that an agent would otherwise have to disambiguate by schema.

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 by stating that 'section' is required and enumerating valid slugs, so an agent can infer this tool fetches one section's headlines. However, there is no explicit when-to-use/when-not guidance and no mention of alternative tools, leaving the choice between this and hindustantimes_news entirely to inference.

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