Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

livemint_headlines

Get recent Mint headlines for a specified section via required slug, including companies, markets, money, ai, or videos. Returns title and URL, with optional summary, author, time, and image.

Instructions

Get Mint section headlines. Returns recent Mint headlines for one section. section is required and takes one of 15 slugs, including companies, markets, money, ai and videos. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesMint 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 discloses the returned fields (title, URL, optional summary/author/time/image), which is meaningful, but says nothing about result limits, pagination, ordering, or whether repeated calls return fresh data.

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, front-loaded sentences with no wasted clauses; the required parameter and return shape come early. Minor redundancy between 'Get Mint section headlines' and 'Returns recent Mint headlines for one section'.

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 single-parameter, non-mutating fetch with no output schema, the description covers the return shape and the required slug, which is what an agent needs to call it correctly. Only pagination/volume behavior is left unaddressed.

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 already lists all 15 slugs, so the schema does the heavy lifting. The description only restates that `section` is required and gives five example slugs, adding no semantics beyond the schema.

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 Mint section headlines') and scopes it to a single section, so an agent knows exactly what it retrieves. It does not name sibling alternatives like livemint_sections or livemint_article, leaving some ambiguity about which live-mint tool to pick.

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?

Usage is implied: 'for one section' plus a required section slug tells the agent when the tool applies. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no routing to the sections or article siblings.

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