Skip to main content
Glama

metacritic_movie_critic_reviews

Read-only

Returns paginated professional/publication reviews for a movie: publication, score, quote, author, and source URL. Credential-free public Metacritic data. slug: Required Metacritic slug, e.g. elden-ring. page: 1-based page number, default 1. Use metacritic_movie to get a Metacritic movie.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "metacritic_movie_critic_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number, default 1.
slugYesRequired Metacritic slug, e.g. elden-ring.
sortNoSort order (critic: date, score, publication; user: date, score, helpful).
per_pageNoResults per page, default 20, clamped to 50.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds one genuinely useful trait beyond the annotations, 'Credential-free public Metacritic data,' but the field list duplicates what the output schema already carries and no rate-limit or pagination-bound behavior is disclosed.

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?

Front-loads the purpose before the credential and routing notes, and every sentence is short. The trailing 'slug: ... page: ...' sentences re-state schema fields and are the only mild redundancy.

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 read-only, credential-free fetch tool with full schema coverage, an output schema, and annotations covering safety, the description supplies everything an agent needs: what it returns, that no auth is required, and which tool produces the required slug.

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 baseline is 3. The description restates the slug requirement/example and the page default, which the schema already documents, and adds no sorting or per_page semantics beyond 'paginated'.

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+resource ('returns paginated professional/publication reviews for a movie') and lists the returned fields. The word 'critic' cleanly distinguishes it from the sibling metacritic_movie_user_reviews, so an agent can route without opening either schema.

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?

Names the companion tool explicitly ('Use metacritic_movie to get a Metacritic movie'), giving clear prerequisite context. It does not state when-not to use this tool versus e.g. metacritic_movie_user_reviews, so it falls short of the 5 benchmark.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.