Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pcgamer_author

Retrieve a PC Gamer author profile by slug or URL, returning biography, job title, social links, and paginated recent articles.

Instructions

Get a PC Gamer author profile. Returns a PC Gamer author profile by slug (for example harvey-randall) or a pcgamer.com author url; supply exactly one. page picks the 1-based page of recent articles (default 1) and overrides a /page/<n> segment in url. The response has name, job_title, biography, social_links, articles, page and has_next_page.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical pcgamer.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. harvey-randall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 behavioral burden well: it states the required one-of parameter constraint, pagination behavior, and the response fields including articles and `has_next_page`. It does not cover error behavior or permissions, so it is strong but not exhaustive.

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 sentences, front-loaded with the core operation and followed by parameter rules and response shape. It is compact and every sentence contributes useful information.

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 three-parameter author-profile lookup with no output schema and no annotations, the description covers input selection, pagination, and return fields. Nothing important for correct invocation appears to be missing.

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 schema already documents the parameters, but the description adds useful semantics: exactly one of `slug`/`url`, `page` defaults to 1, and `page` overrides any `/page/<n>` segment in the URL. This goes beyond the schema descriptions without being redundant enough to lower the score further.

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 and resource: "Get a PC Gamer author profile," then clarifies it returns an author profile by slug or URL. This is clearly distinguishable from sibling article/headline/news tools and from author tools for other sites.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains that exactly one of `slug` or `url` must be supplied and that `page` selects recent-article pages, with override behavior. It gives clear operating context but does not explicitly name alternatives or exclusions such as when to use `pcgamer_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