Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

guardian_article

Fetch a Guardian article by its canonical URL and return structured details: title, section, authors, lead image, timestamps, and body paragraphs.

Instructions

Get Guardian article content. Returns a Guardian article by url, a canonical www.theguardian.com article link. The response has the title, description, section, authors, lead image, publication and update times, and the body as paragraphs. Live-blog timelines are not supported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "guardian_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical www.theguardian.com article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does so well: it enumerates the returned fields and discloses the live-blog limitation. It omits any mention of auth, rate limits, or what happens with a non-canonical or invalid URL.

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: purpose first, then return contents, then the limitation. Front-loaded and every sentence earns its place.

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, the description correctly spells out the response shape (title, description, section, authors, lead image, times, paragraphs). For a single-parameter read tool this is complete.

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` parameter is fully documented there, so the baseline is 3. The description reinforces the canonical www.theguardian.com constraint but adds no syntax or format detail beyond the schema.

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 ('Guardian article content') and the boundary is clear: full article body versus the headlines/topic/author siblings. An agent can tell this retrieves a complete article from a URL without opening the schema.

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?

Provides an explicit when-not-use exclusion ('Live-blog timelines are not supported'), which prevents a failed call. However, it names no alternative or prerequisite for obtaining the canonical URL, so it falls short of full routing guidance.

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