Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metacritic_game_critic_reviews

Fetch a Metacritic game's critic reviews by slug, including publication, score, quote, author, date, platform, and source URL, with sorting and pagination.

Instructions

List a Metacritic game's critic reviews. Lists critic reviews for a Metacritic game by slug (such as elden-ring). Each review has the publication, score, quote, author, date, platform and source URL. sort is date (default), score or publication; page defaults to 1 and per_page to 20 with a max of 50. The response includes the total count.

Input 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",
+  "publication"
+]
  2. Addedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it describes the returned review fields, default sort, pagination defaults/max, and total count. It does not discuss auth, rate limits, or error behavior, but for a read-only list operation it is substantially transparent.

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?

The description is front-loaded and efficient, covering purpose, parameters, and return shape in a compact block. The first two sentences are somewhat repetitive ('List...' then 'Lists...'), which keeps it from being maximally concise.

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?

Given a moderate-complexity list endpoint, rich input schema, and no output schema, the description supplies the missing output context: review fields, total count, sorting, and pagination. An agent has enough information to call it correctly without additional documentation.

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, but the description adds useful parameter meaning beyond the schema: it gives a concrete slug example and specifies that sort defaults to date. It also restates pagination defaults that are already in the schema.

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?

The description names a specific verb and resource: it lists a Metacritic game's critic reviews by slug. The word 'critic' distinguishes it from sibling user-review tools, and 'game' distinguishes it from movie/TV critic-review tools.

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?

It clearly implies the tool is used when you have a game slug and want critic reviews, and it gives an example slug. However, it does not explicitly say when to use this instead of sibling tools such as metacritic_game_user_reviews or metacritic_game, nor does it state prerequisites or exclusions.

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