Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skynews_article

Retrieve Sky News article content by canonical URL to get title, description, section, authors, publication times, image, body paragraphs, and paywalled status.

Instructions

Get Sky News article content. Returns a Sky News article by canonical url of the form https://news.sky.com/story/...-<id>: title, description, section, authors, publication and update times, image, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Sky News article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does well: it enumerates the returned fields (title, description, section, authors, publication/update times, image, body paragraphs) and uniquely discloses the `paywalled` flag. It omits whether the fetch requires auth or how errors (bad URL, removed story) are surfaced, keeping it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the resource and scope front-loaded before the return-value enumeration.

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 compensates by listing the returned structure and flagging the paywall field, which is exactly what an agent needs to decide whether the result is usable.

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% and the schema already says 'Canonical Sky News article URL', but the description adds real meaning by giving the concrete URL pattern with the trailing id, which helps an agent reject non-canonical or search-result URLs.

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 ('Sky News article content') and immediately distinguishes itself from the sibling list/search tools (skynews_headlines, skynews_news, skynews_video) by being a single-article fetch.

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 only implied: the required canonical URL of the form `https://news.sky.com/story/...-<id>` signals that this tool is for retrieving one article whose URL you already have, but the description never says when to use it versus skynews_headlines or skynews_news, nor where to obtain the URL.

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