Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metacritic_movie_user_reviews

Fetch paginated Metacritic movie user reviews by slug, including author, score, quote, date, helpfulness, and spoiler flag. Supports sorting and page limits for public review analysis.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number (default 1)
slugYesMetacritic movie 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

A3.8/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 full behavioral disclosure burden. It meaningfully adds that results are paginated, enumerates the return fields (author, 0-10 score, quote, date, helpfulness, spoiler flag), and states the operation is credential-free. For a simple read-only list tool this is solid disclosure, though it omits details like rate limits or invalid-slug behavior.

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?

Two sentences with zero waste. The verb+resource is front-loaded in the first sentence, and the second sentence efficiently packs return fields and access requirements. 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?

For a 4-parameter list tool with 100% schema coverage, the description covers the essentials: what it returns (field list), how results behave (paginated), and access posture (credential-free). With no output schema, the field enumeration partially compensates. The main gap is guidance on obtaining a valid slug, but the schema documents the parameter adequately.

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 all four parameters are already documented structurally, establishing a baseline of 3. The description adds marginal value beyond the schema: the score scale (0-10) refers to a return field rather than a parameter, and pagination defaults are already in the schema. No significant new parameter semantics are contributed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') and resource ('a Metacritic movie's user reviews'), making the tool's function immediately clear. It implicitly distinguishes from the close sibling metacritic_movie_critic_reviews by specifying 'user' reviews, though it does not name the sibling explicitly. The credential-free note adds context but not differentiation.

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?

The usage context is implied by the resource type — an agent can infer to call this when user reviews of a movie are needed. However, there is no explicit routing among close siblings like metacritic_movie_critic_reviews, metacritic_game_user_reviews, or metacritic_tv_user_reviews; no when-not-to-use guidance or exclusions are provided. 'Credential-free' is an enabling condition, not a selection rule.

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