Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

news18_headlines

Retrieve recent News18 section headlines by slug, returning titles, URLs, and optional summaries, authors, publication times, and images for a chosen news category.

Instructions

Get News18 section headlines. Returns recent News18 stories for one section. section is required and takes one of 18 slugs, such as india, cricket, elections, viral or breaking-news. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesNews18 RSS 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 full burden. It discloses the return shape ('Each item has a title and URL, and may include summary, author, publication time and image'), which is useful, but it omits pagination behavior, rate limits, and any authentication or access constraints.

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?

Four short sentences, front-loaded with purpose and the mandatory parameter before return details. It is efficient, though the final sentence on optional fields could arguably be trimmed without losing much.

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 one-parameter RSS headline tool with no output schema, the description covers the required input and expected return fields. It leaves out pagination or item-count limits, but those may not be relevant for this type of endpoint.

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 18 section slugs. The description repeats example slugs and emphasizes that `section` is required, adding only marginal clarity beyond what the schema provides.

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 ('Get') and resource ('News18 section headlines') with scope ('for one section'). It does not explicitly differentiate itself from sibling tools like news18_news or news18_sections, but the purpose is clear enough for an agent to understand what it returns.

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?

Provides no when-to-use guidance or alternatives. It implies usage by specifying that `section` is required and takes one of 18 slugs, but never says when to choose this tool over news18_news, news18_sections, or other headline tools.

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