mcp-metacritic

Search Metacritic

search_titles

Read-onlyIdempotent

Search Metacritic films, shows, and games by title to find matching entries with critic Metascores in one compact result row, avoiding a second call for the critical verdict.

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

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

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.

Changed8 schema fields changedv2.1.0Oct 30, 2026
- removedOutput schema / properties / results / items / properties / metascore / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / metascore / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / rating / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / rating / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / release_date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / release_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / user_score / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / user_score / type
```
Added value: +[
+  "number",
+  "null"
+]
```
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 cover the safety profile (readOnly, idempotent, openWorld), but the description adds behavior the annotations cannot: no pagination, results always start from the most relevant match, and rows deliberately omit audience score while carrying the Metascore. Those are exactly the facts an agent needs to avoid a redundant second call or a frustrated retry loop.

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?

Front-loaded with the purpose, then return shape, then sibling routing, then constraints, then exclusions – a sensible order with no filler. Every sentence carries a distinct decision-relevant fact.

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?

Despite an output schema existing, the description usefully characterizes what a row contains (compact, critic Metascore, no audience score) and what is missing from it. Combined with the paging and exclusion notes, an agent has everything needed to call it correctly and interpret the result.

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 still adds meaning by framing limit as the sole lever and by stating that results are relevance-ordered rather than paged, which changes how an agent should set it. It does not explain kind semantics beyond the schema's own note, so it stays just above baseline.

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 immediately bounds the scope: "This searches titles only." It explicitly distinguishes itself from get_title, get_reviews and browse_titles, so an agent can route without opening any schema.

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 gives the positive case (title/partial title), the explicit substitution cases (get_title for audience score, browse_titles which does return it, get_reviews for critic write-ups), and the negative cases (cannot find an entry from a plot detail, a person or a studio). The only lever, limit, and the absence of paging are also spelled out.

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

Deploy Server