Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

pcgamer_article

Fetch PC Gamer article content from a canonical pcgamer.com URL, including title, authors, publication times, paywall status, and body paragraphs.

Instructions

Get PC Gamer article content. Returns a PC Gamer article by canonical pcgamer.com url; review pages work the same way as news articles. The response has title, description, section, authors, lead image, publication and update times, a paywalled flag and body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical PC Gamer article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and largely meets it by enumerating the returned fields (title, description, section, authors, lead image, publication/update times, paywalled flag, body paragraphs). The paywalled flag is genuinely useful behavioral context, though auth requirements and failure modes are not addressed.

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, front-loaded with the purpose, followed by the input rule and the return shape. Every clause carries information and nothing is repeated from the schema or annotations.

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 simple single-URL fetch with no annotations and no output schema, the description covers the essentials: what it retrieves, what URL is expected, that reviews and news are treated alike, and what the response contains. Only the absence of error/paywall-access behavior keeps it from a 5.

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?

There is a single parameter with 100% schema description coverage ('Canonical PC Gamer article URL'), so the schema already does the work. The description only echoes the 'canonical' requirement and adds no format or validation detail beyond it, matching the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource ('Get PC Gamer article content' / 'Returns a PC Gamer article') and pins the input to a canonical pcgamer.com URL, which cleanly separates it from listing siblings like pcgamer_headlines or pcgamer_news. It does not name any sibling explicitly, so it stops short of a 5, but an agent can still tell what this fetches.

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: it says review pages work the same way as news articles, which tells the agent both URL types are valid, but it never says where to obtain a canonical URL (e.g. from pcgamer_headlines/news) or when to prefer this over those tools. No exclusions or alternatives are 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