mcp-metacritic

Search Metacritic

search_titles

Read-onlyIdempotent

Find films, shows, and games by title on Metacritic and get their critic Metascore in one compact result list.

Instructions

Search Metacritic for films, shows and games by title. Returns one compact row per match, carrying the critic Metascore, so a question about the critical verdict needs no second call. Search rows carry no audience score: use get_title for that, or browse_titles, which does return it. Use the slug and kind with get_title for the full entry, or with get_reviews for what critics wrote. There is no paging: 'limit' is the only lever, and results always start from the most relevant match. This searches titles only. It cannot find an entry from a plot detail, a person or a studio.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	Restrict results to one catalogue. Metacritic searches all three at once.	any
`limit`	No	How many rows to return.
`query`	Yes	Title or part of one, for example 'the matrix'.

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	Yes
`query`	Yes
`results`	Yes
`total_available`	Yes	How many entries Metacritic counted. For a query of several words it counts entries matching any one of them, so the number is far larger than the useful matches and should not be read as a match count.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv2.0.1Aug 30, 2026
- 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.9/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds valuable behavioral detail: no audience score in rows, no paging, results always start from the most relevant match, and title-only matching. This goes well beyond what annotations alone 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?

Each sentence earns its place: the description covers output shape, missing data, sibling routing, paging behavior, and search scope without redundancy. It is dense but well-structured and front-loaded with the core function.

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?

Backed by a full input schema, an output schema, and strong annotations, the description still contributes deep context: return fields, absence of audience score, sibling usage, slug/kind handoff, no-paging behavior, and title-only limitation. An agent has everything needed to select and invoke this tool correctly.

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 meaning beyond the schema by clarifying that limit is the only paging lever, that results start from most relevant matches, and that kind restricts to one catalogue while Metacritic searches all three. This is helpful but not exhaustive, hence 4.

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 ('Search Metacritic for films, shows and games by title') and describes the compact row output carrying the critic Metascore. It explicitly differentiates itself from siblings by noting it searches titles only, not plot details, people, or studios.

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?

Gives explicit routing guidance: use get_title or browse_titles for audience score, get_title for the full entry, and get_reviews for critic text. It also warns that there is no paging and that limit is the only control, so the agent knows the exact operational constraints.

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

Deploy Server