Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metacritic_browse

Browse Metacritic game, movie, or TV titles by genre and sort by score, 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.

Input 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.5/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 burden. It does disclose the return shape (paginated title cards with Metascore and user score) and the pagination behavior, which is genuinely useful, but says nothing about read-only semantics, auth, or rate limits – acceptable for an obvious read operation but not rich.

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?

Three short sentences, front-loaded with the purpose before the filters and returns. The opening repeats "Browse Metacritic titles" verbatim, a small redundancy, but overall it is tight and well-ordered.

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 supplies the essential return context (paginated cards, Metascore and user score) and covers the filter/sort dimensions, so an agent has enough to call it correctly. Only the sibling-selection guidance is missing.

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 five parameters with enums and defaults. The description restates content type, genre, and sort, but its sort list ("Metascore, popularity, or release date") omits the schema's fourth enum value "oldest", adding no real meaning beyond the schema. Baseline 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 and resource ("Browse Metacritic titles") plus the scoping axis (content type) and returns. It is clear what the tool does, but it never names the sibling metacritic_game/metacritic_movie/metacritic_tv tools it overlaps with, so differentiation is left to inference.

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 "by content type, optionally filtered by genre" – an agent can infer this is the general browse entry point – but there is no explicit when-to-use clause, no when-not clause, and no pointer to the more specific title/review siblings in this large family.

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