Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gamesradar_article

Fetch structured GamesRadar+ article or review content from a canonical URL, returning title, authors, images, and body paragraphs.

Instructions

Get GamesRadar+ article content. Returns one GamesRadar+ article by its canonical gamesradar.com url. The response has the title, description, publish and update times, section, authors, lead image and body paragraphs. Game and hardware review pages work too, taking the author from the page byline when no article-level author exists.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical GamesRadar+ 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 burden and does well: it enumerates the response fields (title, description, publish/update times, section, authors, lead image, body paragraphs) and discloses a non-obvious behavior — that review pages work and the author is taken from the page byline when no article-level author exists. It doesn't mention auth or rate limits, but for a read-only fetch this is solid coverage.

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 tightly written sentences, front-loaded with the core action and return contract, then the review-page edge case. No filler, and the return-field list earns its place given the absence of an output schema.

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 fetch tool with no output schema, the description supplies the return shape and an important edge case, which is nearly complete. Minor gaps remain (no mention of failure modes for non-article URLs or whether the response is ever paginated/truncated), but nothing essential to invoking it 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 description coverage is 100% and there is only one parameter, so the schema already documents the url. The description reinforces that it must be a canonical gamesradar.com URL but adds no format examples or edge-case guidance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (GamesRadar+ article content), and pins down that it returns exactly one article by canonical URL. This clearly distinguishes it from siblings like gamesradar_headlines, gamesradar_news, and gamesradar_sections, which browse rather than fetch a single item.

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 requirement of a canonical url implies the tool is for retrieving a known article, which distinguishes it from the list/browse siblings. However, it never explicitly states when to use this versus gamesradar_headlines or gamesradar_news, nor any prerequisite (e.g., needing a URL from a search or headlines call). Usage is inferable but not spelled out.

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