Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

economictimes_headlines

Retrieve Economic Times headlines for a specified section slug, returning each item's title, URL, summary, publication time, and image.

Instructions

Get The Economic Times section headlines. Returns the latest Economic Times headlines for one section. section is required and takes a slug such as top-stories, markets-stocks, mf-mf-news, industry-banking-finance, jobs-fresher or news-india. Each item has its title, URL, summary, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesEconomic Times section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/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 burden. It usefully discloses the return shape ('title, URL, summary, publication time and image') but says nothing about freshness/latency, rate limits, or any failure behavior for invalid slugs.

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 short sentences, front-loaded with the core purpose, then the scope constraint, then return fields. Minor redundancy between 'Get...headlines' and 'Returns the latest...headlines', but nothing 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?

For a simple read-only retrieval tool with no output schema, the description covers what it returns and that a section slug is required. It is largely complete, with only marginal gaps around invalid input handling.

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 enumerates every valid slug, so the schema does the heavy lifting. The description's slug examples ('top-stories', 'markets-stocks', etc.) restate the enum as illustration rather than adding format or constraint detail, 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 The Economic Times section headlines') and scopes it to 'one section', which distinguishes it from single-article siblings like economictimes_article. It does not explicitly name which sibling to prefer, but the resource is specific enough to route correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for pulling one section's headlines but never states when to use it over economictimes_news, economictimes_article or economictimes_sections. No exclusions or prerequisites are given.

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