Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

forbes_article

Fetch public Forbes article metadata and body content from dated /sites or /councils URLs, preserving HTML headings, paragraphs, and embeds. Does not bypass login or subscription.

Instructions

Forbes article content. Returns public Forbes article metadata and body content. The response preserves rich body HTML, paragraphs, headings, and public embed metadata. Accepts dated /sites//... and /councils//... URLs; it does not bypass login, subscription, or bot challenges.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical HTTPS Forbes article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it declares the content is public, describes the returned structure (metadata plus rich body HTML), and explicitly states the paywall/auth limitation. It omits rate limits, and error behavior for non-article Forbes URLs.

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?

Four short sentences, front-loaded with purpose and return content, then URL acceptance and limitations. No filler; each sentence adds a distinct fact.

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 fetch tool with no annotations or output schema, the description covers purpose, return shape, valid inputs, and the key failure mode. Only edge cases such as error responses or rate limiting are left unspecified.

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 schema already says 'Canonical HTTPS Forbes article URL', which sets the baseline at 3. The description adds real value by enumerating the accepted dated /sites/ and /councils/ URL patterns and the fact that login-gated URLs are out of scope.

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?

The description states a precise verb and resource: it returns Forbes article metadata and body content, and specifies that the body preserves HTML, paragraphs, headings, and embeds. That distinguishes it from Forbes siblings like forbes_headlines or forbes_author and from other publishers' article tools.

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 which URL shapes are valid (/sites/<author>/... and /councils/<council>/...) and that login, subscription, and bot challenges are not bypassed, which frames when the call will and won't succeed. It stops short of naming alternatives such as forbes_headlines for headline-only needs.

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