Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

politico_article

Retrieve article content from a canonical www.politico.com URL, including title, authors, publication times, lead image, and body paragraphs.

Instructions

Get Politico article content. Returns a Politico article by its canonical url, in the form https://www.politico.com/news/YYYY/MM/DD/slug. The response has the title, description, authors, publication and update times, lead image URL and the body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical www.politico.com article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 disclosure burden. It does list concrete response contents (title, description, authors, publication/update times, lead image URL, paragraphs), which is useful behavioral context, but it says nothing about error behavior for invalid/non-canonical URLs, rate limits, or auth requirements.

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 tight sentences, front-loaded with the verb and resource, then the input format, then the return shape. No filler sentences.

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 with no output schema, the description covers input format and return fields adequately. It stops short of documenting failure modes (missing article, malformed slug) or how to obtain a URL in the first place, which would round out completeness.

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% for the single url parameter, so baseline would be 3, but the description adds real value by giving the canonical URL template `https://www.politico.com/news/YYYY/MM/DD/slug`, which helps the agent validate or construct a correct input rather than just echoing the schema's 'Canonical www.politico.com 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 Politico article content' — and names the exact entity (a Politico article keyed by canonical URL). This cleanly separates it from the many sibling tools like politico_headlines, politico_author, politico_topic, and from the hundreds of other publisher *_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: fetch a single article when you already have its canonical URL. However, the description never states when to prefer this over siblings (e.g., use politico_headlines to discover URLs first) and gives no exclusions or prerequisites, so the agent must infer the context.

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