Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

national_article

Fetch The National article content and metadata from a canonical thenationalnews.com URL, reporting paywalls without bypassing access gates.

Instructions

Get The National article content. Returns article metadata and the body served to an anonymous visitor for one canonical The National story URL. The endpoint does not bypass subscriber or access gates and reports paywalled when the page marks content as restricted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical thenationalnews.com article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 full burden and does well: it discloses the anonymous-visitor serving model, that access/subscriber gates are not bypassed, and that the result reports 'paywalled' when content is restricted. It omits pagination/rate-limit or caching behavior, but the critical access limitation is explicit.

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?

Three tight sentences with no waste; the what-it-returns statement and the paywall constraint are front-loaded where they matter most.

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 must cover returns and behavior; it names both the metadata and body returned plus the paywall outcome. What is missing is minor return-shape detail (e.g. field structure), which is acceptable for a single-article fetch 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 coverage is 100% for the single url parameter, so the schema already documents it as a canonical thenationalnews.com URL. The description reinforces the 'canonical' requirement but adds no format or syntax detail beyond the schema, matching the baseline 3 for high-coverage single-param tools.

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 The National article content') and immediately scopes it to one canonical The National story URL, which cleanly separates it from siblings like national_headlines and national_news that cover many stories.

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 makes the intended input context clear ('one canonical The National story URL') and the paywall note implicitly tells the agent this tool is for public article bodies rather than gated content. It does not explicitly name alternatives or state when-not-to-use, 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