Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

thehill_article

Fetch a The Hill article by canonical HTTPS URL and return structured JSON with title, authors, publication times, body paragraphs, and paywall status.

Instructions

Get The Hill article content. Returns one The Hill article by url, which must be a canonical HTTPS thehill.com article link containing a numeric article id. The response has the title, description, section, authors, publication and update times, lead image URL, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Hill 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 full burden and does reasonably well: it discloses the exact URL contract (canonical HTTPS thehill.com link with a numeric article id) and reveals the `paywalled` flag, which is a genuinely useful behavioral trait about content accessibility. It omits auth/permission requirements and what happens on a malformed URL, keeping it from a 5.

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?

Front-loaded with the core action, then two compact follow-on clauses covering the input constraint and the return shape. Every sentence earns its place, though the response-fields list is dense and could be trimmed if an output schema existed.

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 read tool with no output schema and no annotations, the description supplies the missing return-shape detail (title, section, authors, times, image, paragraphs, paywalled flag) and the input contract. Only failure/error behavior is unaddressed.

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, but the description adds real meaning beyond the schema's terse 'Canonical The Hill article URL': it specifies HTTPS, the thehill.com domain, and the requirement of a numeric article id, giving the agent a concrete validity test the schema lacks.

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+resource ('Get The Hill article content') and immediately constrains it to 'one The Hill article by url'. This clearly distinguishes it from sibling list/feed tools like thehill_headlines, thehill_news and thehill_author, which do not return a single full article body.

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 implies usage (fetch a full article given its URL) but never states when to use this versus thehill_headlines or thehill_news, nor any prerequisites for obtaining a valid article URL. Usage is inferable but no alternatives or exclusions are named.

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