Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metacritic_tv_critic_reviews

Get critic reviews for a Metacritic TV show by slug, including publication, score, quote, author, date, and source URL. Sort by date, score, or publication and paginate results.

Instructions

List a Metacritic TV show's critic reviews. Lists critic reviews for a Metacritic TV show by slug (such as breaking-bad). 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 TV show 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, the description carries the full burden, and it does well: it enumerates the returned fields (publication, score, quote, author, date, source URL), discloses the `total` count, and states the pagination cap (max 50). It does not cover error behavior for an unknown slug or any rate limits, so it stops short of a 5.

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 with purpose, then parameters, then return shape — a sensible order. The opening two sentences restate the same fact ('List...' then 'Lists critic reviews for...'), which is the only wasted space.

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?

No output schema exists, so the description must describe the response, and it does: field-by-field review contents plus the `total` count, along with sort and pagination semantics. Nothing an agent needs to call and interpret this list tool 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, but the description adds a concrete slug example and, importantly, the sort default ('`sort` is `date` (default)'), which the schema enum does not state. The page/per_page restatement is largely redundant with the schema, keeping it out of the 5 range.

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 and resource ('List a Metacritic TV show's critic reviews') and names the scoping key ('by `slug`'), which cleanly separates it from the sibling user-review and movie/game review tools. An agent can identify exactly what this returns without opening the schema.

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?

Usage is implied by the required slug and the example ('such as `breaking-bad`'), so an agent knows the entry condition. However, there is no explicit when-to-use guidance or routing against the sibling `metacritic_tv_user_reviews` / `metacritic_tv` tools, so it stays at minimum viable.

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