Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

npr_article

Fetch NPR article content from a canonical www.npr.org URL, returning title, description, section, authors, lead image, timestamps, and body paragraphs.

Instructions

Get NPR article content. Returns an NPR article by canonical url in the form https://www.npr.org/YYYY/MM/DD/...: title, description, section, authors, lead image, publication and update times, and body paragraphs. Tracking query strings and fragments are ignored; other hosts, encoded paths and non-article paths are rejected.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical www.npr.org article URL

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 mostly does: it lists the return payload, discloses that tracking query strings and fragments are ignored (normalization behavior), and states the rejection conditions. It omits any mention of auth or rate limits, but for a public read-only content fetch these are minor.

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?

Front-loads the purpose, then the return fields, then the input-normalization rules. Two dense sentences with no filler; every clause conveys actionable information.

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?

No output schema or annotations exist, so the description correctly enumerates the return fields and the input contract. It is essentially complete for a single-parameter fetch; only auth/error-code behavior is 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%, so baseline is 3, but the description adds real meaning beyond the schema: the exact canonical URL template (https://www.npr.org/YYYY/MM/DD/...), the fact that tracking strings and fragments are stripped, and that non-article/other-host URLs are rejected.

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+resource ('Get NPR article content') and enumerates the returned fields, so an agent knows exactly what the tool produces. It does not explicitly distinguish itself from siblings like npr_headlines, npr_categories or npr_topic, but the article-by-URL framing is unambiguous.

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 description gives accepted input form and rejection conditions (other hosts, encoded paths, non-article paths rejected), which is useful context, but it never says when to call this tool versus the sibling feed/list tools. Usage is implied rather than stated.

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