Skip to main content
Glama
TMDB MCP Server

TMDB MCP Server

Get user reviews

get_reviews
Read-only

Retrieve user reviews for a movie or TV show by TMDB ID, including reviewer name, personal 0–10 rating if provided, and review text.

Instructions

Get user reviews for a movie or TV show: author, that reviewer's own 0-10 rating if they left one (a single person's score, not the aggregate vote_average and not an IMDb/RT/Metacritic value; it can be null), and the review text, clipped to ~1500 characters. Get the id from search_movies/search_tv.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media_type": "<media_type>",
      "id": "<id>"
    },
    "name": "get_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTMDB id of the movie or TV show (as media_type says; from search_movies/search_tv).
pageNo1-based page number for pagination (TMDB returns up to 20 results per page, max 500).
media_typeYesMedia type: 'movie' or 'tv'.

Output Schema

NameRequiredDescriptionDefault
pageYes
resultsYes
total_pagesYes
total_resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • changedInput schema / properties / id / description
      Previous value: -"TMDB numeric id."New value: +"TMDB id of the movie or TV show (as media_type says; from search_movies/search_tv)."
  2. Changed9 schema fields changedv0.14.0
    • removedOutput schema / properties / results / items / properties / author / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / author / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / content / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / content / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / created_at / anyOf
      Previous value: -[
      -  {
      -    "format": "date-time",
      -    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "format": "date-time",
      +    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / results / items / properties / rating / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / rating / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed2 schema fields changedv0.10.1
    • changedOutput schema / properties / results / items / properties / created_at / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "format": "date-time",
      +    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / results / items / properties / created_at / default
      Added value: +null
  4. Addedv0.8.1
  5. Removedv0.8.0
  6. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds behavior the annotations do not: review text is truncated to ~1500 characters and the per-review rating may be null. Both are operationally important (an agent must not treat truncated text as complete or a null rating as a failure).

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?

The tool's purpose and return shape are front-loaded in the first clause, and the prerequisite note is appended last. The long parenthetical disambiguating the rating field is dense but earns its place by preventing a very plausible misreading of the field as an aggregate score.

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?

An output schema exists, so the description need not explain return values, though it helpfully summarizes them. Truncation and nullability are the two surprises an agent would otherwise miss, and both are disclosed. Only a note about pagination behavior when `page` is omitted is absent, and the schema largely covers that.

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 `id`, `media_type`, and `page` are already fully documented; the description adds nothing about `media_type` or pagination beyond that. It repeats the schema's hint about sourcing the id from search_movies/search_tv, which is redundant but harmless. Baseline 3 applies when the schema does the heavy lifting.

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?

"Get user reviews for a movie or TV show" names a specific verb and resource, then enumerates the returned fields (author, per-reviewer rating, review text). It explicitly separates this per-person rating from the aggregate `vote_average` and from IMDb/RT/Metacritic scores, which is exactly the distinction an agent needs to pick this tool over get_ratings or get_movie.

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 rather than stated: an agent can infer it should call this when it needs user-written reviews, and the description gives a concrete prerequisite ("Get the id from search_movies/search_tv"). However, it never states when NOT to use it or names a competing sibling such as get_ratings for aggregate scores, leaving routing partly to inference.

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