Crawlora MCP

timesofindia_headlines

Read-only

Current The Times of India headlines for one public section; section must come from timesofindia_sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "timesofindia_headlines"
  }
}

Input Schema

Name	Required	Description	Default
`section`	Yes	Times of India section slug. Documented values: top-stories, india, world, nri, business, cricket, sports, science, environment, tech, education, entertainment, life-style, astrology, auto, mumbai, delhi, bangalore, hyderabad, chennai, ahmedabad, allahabad, bhubaneswar, coimbatore, gurgaon, guwahati, hubli, kanpur, kolkata, ludhiana, mangalore, mysore, noida, pune, goa, chandigarh, lucknow, patna, jaipur, nagpur, rajkot, ranchi, surat, vadodara, varanasi, thane, thiruvananthapuram, us, pakistan, south-asia, uk, europe, china, middle-east, rest-of-world.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / section / description

Added value: +"Times of India section slug. Documented values: top-stories, india, world, nri, business, cricket, sports, science, environment, tech, education, entertainment, life-style, astrology, auto, mumbai, delhi, bangalore, hyderabad, chennai, ahmedabad, allahabad, bhubaneswar, coimbatore, gurgaon, guwahati, hubli, kanpur, kolkata, ludhiana, mangalore, mysore, noida, pune, goa, chandigarh, lucknow, patna, jaipur, nagpur, rajkot, ranchi, surat, vadodara, varanasi, thane, thiruvananthapuram, us, pakistan, south-asia, uk, europe, china, middle-east, rest-of-world."

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that results are 'current' and section is 'public', a modest freshness/scope hint; it says nothing about result limits, ordering, or rate behavior, which is acceptable given the annotation coverage.

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?

A single tight sentence with the scope stated first and the section-source constraint second. No filler; every clause earns its place.

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?

For a one-parameter read-only feed with an output schema present and no pagination concerns raised, the description covers purpose, scope, and valid-input sourcing adequately. It lacks only explicit sibling guidance, which keeps it from being fully complete.

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 schema already enumerates every documented section slug. The description's added value is pointing to timesofindia_sections as the authoritative source for valid values, a mild but useful supplement, so baseline 3 is appropriate.

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?

The description states a specific verb/resource combination: current Times of India headlines scoped to one public section. This clearly separates it from a single-article tool, but it does not explicitly name or contrast against the other headlines-adjacent siblings (timesofindia_news, timesofindia_article), leaving differentiation to inference.

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?

It gives a concrete prerequisite: 'section must come from timesofindia_sections,' routing the agent to the correct sibling for valid inputs. It stops short of stating when to prefer this tool over timesofindia_news or any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?