Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

huffpost_headlines

Fetch current HuffPost section headlines by passing a required section slug, like news/politics or life/travel. Returns each item's title, URL, and image.

Instructions

Get HuffPost section headlines. Returns current HuffPost headlines for one topic hub. section is required and takes a slug that can include a path, such as news/politics, impact/green, entertainment/tv, life/travel or voices/black-voices. Each item has its title, URL and image. Summary, author and publication time are not returned.

Input Schema

NameRequiredDescriptionDefault
sectionYesHuffPost section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/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, and it does disclose the return payload (title, URL, image) plus an explicit negative list (summary, author, publication time are not returned). That negative disclosure is genuinely useful with no output schema. It still omits pagination, item count, and any rate/auth notes.

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 the verb and resource, then parameter format, then return shape. Every sentence carries information; the final 'not returned' sentence is mildly defensive but earns its place by bounding expectations.

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 headline fetcher with no output schema and no annotations, the description covers purpose, parameter format, and return contents adequately. The remaining gap is volume/pagination behavior, which is minor for this tool class.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum already enumerates every valid slug, so the baseline is 3. The description adds value beyond the schema's terse 'HuffPost section slug' by explaining that a slug may include a path and giving concrete path-form examples, clarifying the format rather than just restating it.

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 and resource ('Get HuffPost section headlines') and scopes it to exactly one topic hub. It is clear on its own but never names or contrasts with the obvious siblings (huffpost_news, huffpost_sections, huffpost_article), so an agent must infer the division of labor.

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?

'for one topic hub' and '`section` is required' imply the usage context, and the slug examples hint at the granularity expected. However there is no explicit when-to-use-this vs when-to-use huffpost_news/huffpost_sections guidance, so routing relies on inference.

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