mcp-metacritic

Browse rankings

browse_titles

Read-onlyIdempotent

Find films, shows, or games ranked by critic score, release date, or popularity. Filter by genre to narrow results and discover top-rated or trending titles.

Instructions

List films, shows or games by score, by release date or by current popularity. Use this when there is no specific title to look up: best rated, newest, what people are looking at now. Filter by genre with a single name such as Horror, Comedy or Action. Sorting by score returns the all-time ranking, which is dominated by older titles: combine with a genre to narrow it. Scores come back on their own scales, 100 for critics and 10 for users. Paging is approximate: Metacritic does not order tied entries stably, so an entry can appear on two consecutive pages. Deduplicate by slug rather than counting rows.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	Which catalogue to list.	movie
`sort`	No	'score' is the critic ranking, 'recent' is by release date, 'popular' is current attention.	score
`genre`	No	Single genre name, such as Horror. Omit for all genres.
`limit`	No	How many rows to return.
`offset`	No	How many rows to skip, for paging.

Output Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes
`sort`	Yes
`genre`	Yes
`notes`	Yes
`offset`	Yes
`results`	Yes
`next_offset`	Yes	Pass as 'offset' for the next page. Tied entries are not ordered stably upstream, so deduplicate by slug across pages.
`total_available`	Yes	How many entries match upstream, which is the size of what this samples.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv2.0.1Aug 30, 2026

addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

addedOutput schema / properties / genre / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / genre / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

changedOutput schema / properties / next_offset / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / offset / minimum
```
Added value: +-9007199254740991
```
addedOutput schema / properties / results / items / properties / id / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / results / items / properties / id / minimum
```
Added value: +-9007199254740991
```

addedOutput schema / properties / results / items / properties / metascore / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / results / items / properties / metascore / type
```
Removed value: -[
-  "number",
-  "null"
-]
```

addedOutput schema / properties / results / items / properties / rating / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / results / items / properties / rating / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
addedOutput schema / properties / results / items / properties / release_date / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedOutput schema / properties / results / items / properties / release_date / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / results / items / properties / user_score / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / results / items / properties / user_score / type
```
Removed value: -[
-  "number",
-  "null"
-]
```

changedOutput schema / properties / results / items / properties / year / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / total_available / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / total_available / minimum
```
Added value: +-9007199254740991
```

First observedv1.0.0Aug 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark the tool as read-only and idempotent, but the description adds critical behavioral detail: scores arrive on different scales (100 vs 10), paging can be unstable for tied entries, and deduplication should be done by slug rather than row count. This goes well beyond what annotations or schema convey.

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?

The description is dense but every sentence earns its place: purpose, usage context, caveats about ranking composition, score scales, paging instability, and deduplication are all essential. It is front-loaded with the main action and use case.

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?

For a read-only listing tool with an output schema, the description covers all necessary operational context: when to use it, how to narrow results, what the ranking means, and how to handle paging anomalies. Nothing critical 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 parameters are already fully documented in the schema. The description reinforces genre usage and sort meanings but does not meaningfully add new parameter-level information beyond 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?

The description clearly states a specific verb ('List') and resource ('films, shows or games'), plus the three ranking dimensions. It distinguishes itself from the sibling lookup tools by explicitly saying 'when there is no specific title to look up.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains when to use the tool versus looking up a specific title, and gives concrete guidance: combine with a genre to narrow the all-time ranking, expect approximate paging, and deduplicate by slug. This is actionable and prevents misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server