Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegraph_article

Fetch The Telegraph article content by canonical URL, returning title, section, authors, publication details, image, paragraphs, and paywall status; blocked pages return an error.

Instructions

Get The Telegraph article content. Returns one The Telegraph article by url, a canonical HTTPS article link. The response has the title, description, section, authors, publication and update times, image URL, body paragraphs and a paywalled flag. Access is intermittent, and subscriber-only or blocked pages return an error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Telegraph article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 behavioral burden and does so well: it discloses that access is intermittent and that subscriber-only or blocked pages return an error, plus a `paywalled` flag in the response. It stops short of detailing rate limits or retry behavior, keeping it at a strong 4 rather than 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?

Three sentences, front-loaded with purpose, then the return shape, then access caveats. Every sentence earns its place with no filler, though the field enumeration is slightly list-like.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description fully compensates: it enumerates the response fields (title, description, section, authors, times, image URL, paragraphs, paywalled flag) and covers failure behavior. Nothing an agent needs to call and interpret the result is missing.

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% and the single `url` param is already documented as 'Canonical The Telegraph article URL'. The description adds only a minor format hint ('canonical HTTPS article link'), so the schema does the heavy lifting and the baseline 3 applies.

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 (Get) and resource (The Telegraph article content) and scopes it to a single article fetched by URL, which naturally distinguishes it from sibling list/browse tools like telegraph_headlines, telegraph_news, and telegraph_sections. An agent can tell exactly what it retrieves.

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 by the single-URL fetch shape, but the description never states when to choose this over alternatives such as telegraph_headlines or telegraph_news, nor when a URL is or isn't valid. No explicit when/when-not guidance is given.

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