Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gamesradar_author

Fetch a GamesRadar+ author profile by slug or URL, returning name, job title, bio, social links, and one page of articles.

Instructions

Get a GamesRadar+ author profile. Returns a GamesRadar+ author profile, found by slug (for example rosalie-newcombe) or by url; send exactly one. page (1-based, default 1) overrides any page in the URL. The response has the name, job title, biography, social_links, one page of articles, page and has_next_page.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical gamesradar.com/author/<slug> URL, optionally with a /page/<n> segment; alternative to slug
pageNo1-based page number; overrides any page number in url
slugNoAuthor slug, e.g. rosalie-newcombe

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 discloses that the operation is a read ('Get'), lists the exact response fields, explains pagination behavior, and says page overrides any URL page. It does not mention auth needs or rate limits, but for a public profile read this is a minor omission.

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?

Purpose is front-loaded and the description is appropriately sized. The first two sentences are slightly redundant ('Get...' then 'Returns...'), but the remaining structure efficiently covers identification, pagination, and response contents.

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?

For a simple author-lookup tool with no output schema and no annotations, this is complete: it explains how to identify the author, that exactly one of slug/url must be sent, how pagination works, and what the response contains. No critical gap remains for correct invocation.

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%, so the baseline is 3. The description adds meaningful value by resolving an ambiguity in the schema (required is empty, yet the description says 'send exactly one' of slug/url) and restates the page-override rule, which directly affects correct invocation.

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 a GamesRadar+ author profile' and repeats that it returns an author profile. This clearly separates it from article/news/headlines siblings by resource, but it never names or contrasts those alternatives, so it stops short of full sibling differentiation.

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 description implies usage by stating it retrieves an author profile and gives invocation rules ('send exactly one' of slug or url). However, it offers no explicit when-to-use guidance or when-not conditions relative to gamesradar_article, gamesradar_headlines, or other siblings.

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