Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

propublica_article

Retrieve structured ProPublica article data by canonical URL, including title, authors, dates, description, image, section, paywall status, and body text.

Instructions

Get ProPublica article content. Returns a ProPublica article by canonical url (propublica.org/article/<slug>): title, authors, publication and update dates, the dek as description, lead image where available, section, a paywalled flag and the body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical ProPublica article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the `paywalled` flag and notes the lead image is only present 'where available', but it says nothing about authentication, rate limits, or whether paywalled bodies are still returned.

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?

Two sentences, purpose front-loaded, followed by the return shape. No filler and nothing that fails to earn its place.

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 does the necessary work of enumerating the returned fields (title, authors, dates, dek, image, section, paywalled, paragraphs). It stops short of clarifying behavior for paywalled articles, which is the one remaining gap for a single-param detail tool.

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 the baseline is 3, and the description goes beyond the schema's generic 'Canonical ProPublica article URL' by spelling out the exact format `propublica.org/article/<slug>`. That format guidance is genuinely additive for constructing a valid call.

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 (Get) and resource (ProPublica article content) plus the canonical URL form, which implicitly separates it from the sibling list endpoints (propublica_headlines, propublica_news, propublica_sections). It never names a sibling explicitly, so an agent gets clear purpose but not explicit differentiation.

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 requirement of a canonical `url` implies this is a detail-fetch used after obtaining a link, but the description gives no explicit when-to-use, no guidance on where to source the URL, and no comparison to propublica_headlines/news. Usage is only inferable.

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