Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gamesradar_headlines

Fetch GamesRadar+ section headlines by slug, returning titles, URLs, types, author, publication time, and image if available.

Instructions

Get GamesRadar+ section headlines. Returns the latest GamesRadar+ headlines for one section. section is required and takes one of 21 slugs such as games, games-reviews, hardware-news, entertainment-tv, lego or dungeons-and-dragons. Each item has its title, URL and type, plus publication time, author and image when the section page shows them.

Input Schema

NameRequiredDescriptionDefault
sectionYesGamesRadar+ 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, the description carries the full burden and does reasonably well: it discloses that items contain title, URL, `type`, and conditionally publication time, author, and image. It omits any note on freshness guarantees, rate limits, or auth, but the return-shape disclosure is genuinely useful given there is no output schema.

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 front-loaded sentences with no padding; the section requirement and slug options come early. The first two sentences slightly overlap ("Get ... headlines" / "Returns the latest ... headlines"), a minor redundancy.

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 one-parameter read tool with no output schema and no annotations, the description covers the input constraint (required section, 21 slugs) and the returned fields adequately. No output schema exists, so return-value explanation is not expected, and little essential context 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 coverage is 100% and the enum already lists all 21 slugs with a field description. The description's slug examples (games, games-reviews, hardware-news, etc.) largely restate enum values, so it adds color but little beyond what the schema provides.

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?

States a specific verb and resource ("Get GamesRadar+ section headlines") and constrains scope to a single section. However, it never distinguishes itself from close siblings like gamesradar_news, gamesradar_sections, or gamesradar_article, so an agent must infer the boundary.

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 tool fetches headlines for a given section, and the description notes `section` is required. There is no when-to-use/when-not guidance and no mention of when to prefer gamesradar_news or gamesradar_article instead.

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