Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gamerant_author

Fetch a Game Rant author's name, bio, social links, and recent articles from a canonical author URL. Rejects paginated URLs, so older posts are excluded.

Instructions

Get a Game Rant author profile. Returns a Game Rant author profile for a url of the form https://gamerant.com/author/<slug>/. The response has the name, title, image, biography, social_links (type and URL) and about 20 latest articles. Paginated author URLs are rejected, so older articles are not available.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Game Rant author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does a good job: it enumerates the returned fields (name, title, image, biography, social_links, ~20 latest articles) and discloses a real limitation (paginated author URLs rejected, older articles unavailable). It omits auth/rate-limit behavior, but for a read-only scrape this is strong disclosure.

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 purpose, then the input format, then the return contents and caveat. No filler or repetition.

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?

No output schema or annotations exist, so the description must cover behavior and returns, which it largely does by listing the response fields and the pagination limitation. Slightly more on throughput or error behavior would make it fully self-contained, but nothing essential is missing for calling it.

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% ("Canonical Game Rant author URL"), so the baseline is 3, but the description goes beyond it by giving the exact URL template `https://gamerant.com/author/<slug>/` and the constraint that paginated variants are rejected. This meaningfully improves how the agent constructs the input.

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 Game Rant author profile") and names the publisher, which cleanly separates it from the gamerant_article, gamerant_headlines, gamerant_news and gamerant_sections siblings. An agent can identify the resource type without opening the schema.

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 implied by the required canonical author URL format and the note that paginated URLs are rejected. However, there is no explicit routing guidance such as "to retrieve a specific article instead, use gamerant_article", so the agent must infer when this tool applies versus its 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