Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metacritic_movie_user_reviews

Retrieve paginated user reviews for a Metacritic movie, including author, score, quote, date, helpfulness, and spoiler flag, with sorting by date, score, or helpfulness.

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.

Input 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.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose that results are paginated and enumerates the returned fields, which is real behavioral context. However, it says nothing about permissions, rate limits, or total-count behavior, leaving meaningful gaps for a no-annotation tool.

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 tightly written sentences with zero waste, front-loading the operation and then the return shape. Nothing is redundant or padded.

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?

With no output schema, the description usefully enumerates the returned fields (author, score, quote, date, helpfulness, spoiler flag), compensating well for the absent output schema, and parameters are fully covered by the schema. Minor gap: no guidance on pagination limits or total pages, but the core contract for a simple read tool is complete.

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 (slug, page, per_page, sort) are already documented in the schema, including the enum for sort and the per_page max. The description adds no syntax or format detail beyond that, matching the baseline of 3.

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?

States a specific verb ('List') and resource ('Metacritic movie's user reviews'), and the word 'user' inherently separates it from the sibling metacritic_movie_critic_reviews. It does not explicitly name or contrast against any sibling, keeping it just short of a 5.

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 purpose implies when to reach for it (fetching audience reviews for a given movie slug), but there is no explicit when-to-use, when-not, or alternative routing to metacritic_movie or the critic-reviews tool. Usage is left to inference.

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