Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

forbes_headlines

Fetch up to 50 unique Forbes article cards for a section path, including title, URL, author, description, publication time, and image when present.

Instructions

Forbes section headlines. Returns up to 50 unique Forbes article cards for one navigation path. section is required and takes a path value from the Forbes categories endpoint, such as /business/. Each card has the title, article URL, description, author, and publication time and image URL when present. A blocked section returns an error, not an empty list.

Input Schema

NameRequiredDescriptionDefault
sectionYesForbes navigation path from /forbes/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 reasonably well: it discloses the 50-item cap, uniqueness of cards, the shape of each returned card, and a non-obvious error behavior (blocked section returns an error rather than an empty list). It omits auth needs and rate limits, but the error semantics are a genuinely useful disclosure.

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?

The purpose is front-loaded in the opening clause, followed by scope, parameter requirement, return shape, and edge-case behavior. Almost every sentence delivers distinct information with no padding.

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 one-parameter tool with full schema coverage and no output schema, the description supplies the return-card fields and error behavior, which is what an agent needs. It is nearly complete, only missing auth/rate-limit context that a no-annotation tool would ideally surface.

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%, so the parameter is already fully documented. The description adds an illustrative value ('/business/') and reinforces the source of valid paths, but this largely restates what the schema already says, keeping it at the baseline for well-covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Forbes section headlines') and the exact scope: up to 50 unique article cards for one navigation path. This clearly distinguishes it from siblings like forbes_article (single article), forbes_categories (path source), and forbes_billionaires.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent that `section` is required and must be a path value from the Forbes categories endpoint, which implicitly routes to forbes_categories as the prerequisite. However, it never explicitly names that sibling or states when NOT to use this tool, so it stops short of full when/when-not guidance.

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