Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

businessinsider_headlines

Fetch headlines from one Business Insider section by passing its slug, returning titles, URLs, summaries, authors, times, and images.

Instructions

Get Business Insider section headlines. Returns fresh headlines for one Business Insider section. section is required and is one of business, markets, technology, politics, strategy, finance, science, lifestyle or reviews. Each item has a title and URL, and may also carry a summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesBusiness Insider 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 full burden. It usefully discloses the return shape (title, URL, optional summary/author/time/image), which is real behavioral context, but omits auth needs, rate limits, and freshness semantics beyond the vague 'fresh headlines.'

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?

Front-loaded with the purpose in the first sentence, then return details. The inline enumeration of all nine section slugs duplicates the schema and is mildly wasteful, but the three sentences are otherwise tight.

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 headline fetcher with no output schema, the description covers input constraints and the shape of returned items. Nothing critical is missing, though read-safety and pagination are unstated.

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 only parameter has an enum, so the schema already documents it fully. The description repeats the enum values verbatim without adding format or selection guidance beyond what the schema provides, matching the baseline 3.

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 Business Insider section headlines') and scopes it to one section. Clear enough to distinguish from businessinsider_news or businessinsider_article, though it does not explicitly name those siblings.

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 only implied by 'for one Business Insider section.' There is no explicit when-to-use vs when-not, no mention of siblings like businessinsider_sections or businessinsider_news, and no prerequisites (e.g., whether section must be spelled exactly).

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