Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

huffpost_article

Retrieve HuffPost article content by canonical URL to get title, description, section, authors, lead image, publish/update times, paragraphs, and paywall status.

Instructions

Get HuffPost article content. Returns a HuffPost article by url, a canonical huffpost.com/entry/<slug>_<type>_<id> link. The response has the title, description, section, authors, lead image, publish and update times, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical HuffPost article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 enumerates the returned fields (title, description, section, authors, lead image, publish/update times, paragraphs, paywalled flag). It stops short of explaining error behavior, rate limits, or whether body paragraphs are truncated for paywalled articles.

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?

Three short sentences: purpose first, then input format, then return shape. Efficient and front-loaded, with only slight redundancy between "Get HuffPost article content" and "Returns a HuffPost article".

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 output schema, the description correctly supplies the return value summary, and it documents the single required input. It lacks error/paywall-body behavior, but for a simple read-by-URL tool it is close to complete.

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%, so baseline is 3, but the description adds real value by spelling out the expected URL shape (`huffpost.com/entry/<slug>_<type>_<id>`), guiding the agent beyond the schema's bare "Canonical HuffPost article URL".

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 and resource ("Get HuffPost article content") and pins the scope to a single article fetched by canonical URL, which cleanly separates it from the sibling listing tools (huffpost_headlines, huffpost_news, huffpost_sections, huffpost_author).

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 need for a canonical huffpost.com/entry URL implies the usage scenario, but there is no explicit when-to-use/when-not guidance and no mention of the sibling tools it complements or excludes. An agent can infer the use case but must rely 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