Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metacritic_browse

Browse Metacritic titles by content type, filter by genre, and sort by Metascore, popularity, or release date. Returns paginated cards with Metascore and user score.

Instructions

Browse Metacritic titles. Browse Metacritic titles by content type, optionally filtered by genre and ordered by Metascore, popularity, or release date. Returns paginated title cards with Metascore and user score. Credential-free public Metacritic data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number (default 1)
sortNoSort order
typeYesContent type
genreNoGenre filter (e.g. Action)
per_pageNoResults per page (default 24, max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "score",
+  "popularity",
+  "release_date",
+  "oldest"
+]
    • addedInput schema / properties / type / enum
      Added value: +[
+  "game",
+  "movie",
+  "tv"
+]
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explicitly states 'Credential-free public Metacritic data' and discloses the paginated return shape with 'Metascore and user score'. It does not describe output structure beyond that, but this is meaningful transparency for a read-only browse tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences and roughly 35 words, with the core behavior front-loaded. However, the opening sentence 'Browse Metacritic titles.' is redundant with the second sentence and the tool name, so not 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 simple read-only listing tool with no output schema, this description covers the essentials: content type, optional genre filtering, sort dimensions, paginated return cards with scores, and credential-free public access. It could add sibling routing or more return-field detail, but nothing critical is missing 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 coverage is 100%, so the schema already documents all five parameters. The description adds useful context by noting genre is optional and mapping sort to Metascore, popularity, or release date, but it mostly restates schema semantics and omits the 'oldest' sort option present in the enum.

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 action (browse), resource (Metacritic titles), and the main axes: content type, genre filter, sort order, and score output. It is clear enough to distinguish from review/detail siblings like metacritic_game_critic_reviews, though it does not explicitly name an alternative.

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 a browsing/list use case by describing content-type filtering, genre filtering, and sorting, but it gives no explicit when-to-use versus alternatives or exclusions. It does not route the agent to metacritic_game, metacritic_movie, or metacritic_tv when detailed title information is needed.

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