Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hbr_headlines

Fetch Harvard Business Review headlines from its site-wide stream, returning titles, URLs, summaries, topics, content types, authors, and images for editorial monitoring.

Instructions

Get Harvard Business Review latest headlines. Returns the latest items from Harvard Business Review's site-wide The Latest stream, with no parameters. Each item has its title, url, summary, topic, content_type (for example Digital Article), and authors and an image_url when available. Items carry no publication time.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose the source stream, the shape of returned items (title, url, summary, topic, content_type, authors, image_url when available), and the notable caveat that 'Items carry no publication time.' It omits result-count limits and pagination behavior, which an agent would need to know.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and the source stream, then the payload. The field enumeration earns its place because there is no output schema to carry it.

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?

With no annotations and no output schema, the description supplies the missing return-value detail and the no-params fact, so an agent can call and interpret it. The remaining gap is operational: how many items are returned and whether the list is capped.

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?

The tool takes zero parameters, which is the baseline-4 case. The description confirms this explicitly ('with no parameters'), removing any doubt about whether an argument is expected.

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 Harvard Business Review latest headlines') and pins the scope to HBR's site-wide 'The Latest' stream. That scoping implicitly separates it from the topic-filtered hbr_topic and item-level hbr_article, but no sibling is named, so the differentiation is left to inference.

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?

The 'with no parameters' and 'site-wide' wording signals that this is the unfiltered, no-input variant, which implies a use case versus filtered siblings like hbr_topic. However, it never states when to prefer this over hbr_topic or hbr_categories, so usage is only implied.

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