Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metacritic_movie_critic_reviews

Fetch paginated Metacritic critic reviews for a movie by slug, including publication, score, quote, author, and source URL. Sort and page through public review data.

Instructions

List a Metacritic movie's critic reviews. Returns paginated professional/publication reviews for a movie: publication, score, quote, author, and source URL. 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",
+  "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 provided, the description carries the full burden of behavioral disclosure. It adds useful context: the tool returns paginated results, lists the specific fields returned, and states it is credential-free public data. It does not cover rate limits or failure modes, but for a simple read-only list operation, it provides meaningful behavioral transparency beyond the schema.

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 wasted words. The action and resource are front-loaded, followed by concise detail on return contents and auth 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 tool with no output schema, the description compensates by enumerating the returned fields. It also covers auth status and pagination, which an agent needs to know. It does not explain how to obtain a slug or what happens for invalid slugs, but those are minor gaps given the sibling ecosystem and clear schema. Overall it is adequate for correct invocation.

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 four parameters. The description does not add any meaning beyond the schema; it mentions 'publication, score, quote, author, and source URL' but these are output fields, not parameter semantics. Per calibration, baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ("List"), a precise resource (a Metacritic movie's critic reviews), and even enumerates the return fields (publication, score, quote, author, source URL). It clearly distinguishes itself from sibling tools by specifying 'movie' and 'critic reviews,' as opposed to game/tv or user reviews.

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 establishes clear context: this is for professional/publication critic reviews of a Metacritic movie, implying it is not for user reviews or non-movie media. However, it does not explicitly name alternatives like metacritic_movie_user_reviews or metacritic_game_critic_reviews, nor does it state when not to use it. This is clear enough but lacks explicit routing.

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