Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metacritic_movie_critic_reviews

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

Instructions

List a Metacritic movie's critic reviews. Lists critic reviews for a Metacritic movie by slug (such as oppenheimer). Each review has the publication, score, quote, author, date 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 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.1/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses the return fields (publication, score, quote, author, date, source URL), the pagination defaults/max, and the total count. It omits any auth/rate-limit context, but for a read-only list operation the disclosure is solid.

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-loaded and efficient overall, but the opening is redundant: 'List a Metacritic movie's critic reviews' is immediately restated by 'Lists critic reviews for a Metacritic movie by slug.' One sentence could be trimmed.

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 list tool with no output schema, the description covers the key return fields, pagination semantics, and total count, which is what an agent needs. It could be stronger by noting how it relates to sibling review/metadata tools, but nothing essential is missing.

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; the description adds the concrete slug example ('oppenheimer') which clarifies the expected format beyond the schema's terse 'Metacritic movie slug'. Sort enum values and pagination defaults largely restate 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?

States a specific verb 'List' and the exact resource 'critic reviews for a Metacritic movie' keyed by slug. This cleanly distinguishes it from siblings like metacritic_movie_user_reviews (user vs critic) and metacritic_movie itself.

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 description implies when to use it (to get a movie's critic reviews given a slug) but names no alternatives or conditions. It never tells the agent to prefer metacritic_movie_user_reviews for user reviews or metacritic_movie for overall metadata, leaving routing to inference from the name.

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