Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pcgamer_headlines

Retrieve recent PC Gamer headlines for a required section slug—deals, games, gaming-industry, guides, hardware, movies-tv, news, or software—returning titles and URLs.

Instructions

Get PC Gamer section headlines. Returns recent PC Gamer headlines for one section. section is required and takes one of eight slugs: deals, games, gaming-industry, guides, hardware, movies-tv, news or software. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesPC Gamer section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does useful work: it discloses the return shape (title and URL, optionally summary, author, publication time and image). It does not mention result count, pagination, or rate limits, but for a simple read feed it covers the behavior an agent most needs.

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 compact sentences, front-loaded with the purpose before the parameter and return details. Nothing is wasted, though the slug enumeration partially duplicates the schema's enum rather than adding new information.

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?

There is no output schema, so the description must and does describe the returned fields, and it names the required parameter with its allowed values. For a single-parameter read tool this is essentially complete; only minor operational details (count, ordering, pagination) are absent.

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 the single parameter is a fully-enumerated string, so the schema already documents everything. The description restates the same eight slugs, adding no format or semantic detail beyond the enum, which is the baseline 3 case.

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 section headlines') and scopes it to a single section, so an agent knows exactly what it fetches. It does not, however, differentiate itself from close siblings like pcgamer_news or pcgamer_sections, which share the same publisher resource.

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 `section` parameter and the 'one section' phrasing suggest this is the per-section headline feed, but no alternative tool is named and no when-to-use/when-not guidance is given. An agent must infer the choice against pcgamer_news/pcgamer_article on its own.

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