Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

metacritic_game_user_reviews

Retrieve paginated user reviews for a Metacritic game, including scores, quotes, and dates. Use for sentiment analysis and player feedback.

Instructions

List a Metacritic game's user reviews. Returns paginated user reviews for a game: author, score (0-10), quote, date, platform, helpfulness, and spoiler flag. Credential-free public Metacritic data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number (default 1)
slugYesMetacritic game slug
sortNoSort order
per_pageNoResults per page (default 20, max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
      +  "date",
      +  "score",
      +  "helpful"
      +]
  2. Addedv1.5.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions pagination and the returned fields (author, score, quote, etc.) and states credential-free access, which is useful. However, it doesn't disclose pagination details (default page size, limits) beyond what's in the schema, nor error behavior. This is adequate but leaves some gaps.

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 concise sentences with no fluff. The purpose is front-loaded, and the return fields are listed succinctly. Every sentence earns its place.

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?

Given the tool's simplicity and the schema covering all parameters, the description is nearly complete. It lists the output fields and mentions pagination and public access. It could briefly mention sorting options (already in schema) or not found behavior, but these are minor for a list endpoint.

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%, so the schema already documents all parameters. The description adds no additional semantic meaning about parameters, only lists output fields. Baseline 3 is appropriate since the description doesn't need to compensate.

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?

Description states a clear verb ('List') and resource ('Metacritic game's user reviews'), and lists the returned fields, distinguishing it from sibling tools like metacritic_movie_user_reviews and metacritic_game_critic_reviews. The scope is unambiguous.

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?

The description clearly conveys the tool's purpose (reading user reviews for a specific game) and notes it's credential-free public data. While it doesn't explicitly name alternatives or exclusions, the distinction is inferable from the tool name and context.

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