Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wapo_article

Retrieve public Washington Post article content and metadata from a canonical URL, returning body paragraphs as structured JSON. Note: metered articles are excluded.

Instructions

Get a Washington Post article's content. Returns one public Washington Post article's metadata and body paragraphs from a canonical article URL. Metered articles that the site truncates are not available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Washington Post article URL

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 provided, the description carries the behavioral burden. It discloses the output type (metadata and body paragraphs) and an important limitation (metered/truncated articles are unavailable). It does not cover error behavior, authentication, or rate limits, but for a simple read-style tool this is reasonably transparent.

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 description is three concise sentences with no filler. It front-loads the core action and output, then states the key limitation. Every sentence adds 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?

This is a simple one-parameter tool with no output schema, so the description's mention of metadata and body paragraphs is sufficient to convey the return shape. It also covers the main availability constraint. Exact metadata fields and failure behavior are unspecified, but the definition is generally complete for selecting and invoking the tool.

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%: the only parameter, url, is already described as 'Canonical Washington Post article URL.' The description repeats this and adds the 'public' constraint, but does not provide deeper parameter semantics beyond what the schema already offers.

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 uses a specific verb and resource: 'Get a Washington Post article's content.' It further clarifies scope by stating it returns one public article's metadata and body paragraphs from a canonical URL, which clearly distinguishes it from sibling tools like wapo_headlines, wapo_news, and wapo_sections.

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?

The description provides clear usage context: supply a canonical article URL and only public articles are supported. It also gives an explicit exclusion: metered articles that the site truncates are not available. It does not name alternative tools, so it stops short of a 5.

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