TMDB MCP Server

Overview Schema Source Related Servers Discussions Admin

Get TV episode

get_tv_episode

Read-only

Fetch one TV episode by show ID, season, and episode number: overview, air date, runtime, TMDB vote average, guest stars, director/writer, plus its IMDb ID for per-episode ratings.

Instructions

Get one episode of a TV show by show id + season number + episode number: overview, air date, runtime, TMDB vote average (vote_average, TMDB's own 0-10 user score — not an IMDb/RT/Metacritic score; get_movie/get_tv's ratings are whole-show only and this tool makes no OMDb call), guest stars (up to 15) and director/writer. Also returns the episode's own imdb_id/imdb_url — pass that id to get_ratings for this one episode's IMDb rating, the only way to get a per-episode IMDb score here. Get the show id from search_tv.

Input Schema

Name	Required	Description
`id`	Yes	TMDB numeric id.
`season_number`	Yes	Season number (0 = specials).
`episode_number`	Yes	Episode number within the season.

Output Schema

Name	Required	Description
`crew`	Yes
`name`	Yes
`imdb_id`	Yes	This episode's own IMDb id (not the show's) — pass it to get_ratings for the episode's IMDb rating, which no TMDB field carries. Null when TMDB has no IMDb id for it.
`air_date`	Yes
`imdb_url`	Yes
`overview`	Yes
`still_url`	Yes
`guest_stars`	Yes
`vote_average`	Yes	TMDB's own 0-10 user score. A different audience and scale from the IMDb/RT/Metacritic scores get_movie/get_tv return as `ratings` — don't compare, average or substitute across the two.
`season_number`	Yes
`episode_number`	Yes
`runtime_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv0.14.0Oct 24, 2026

removedOutput schema / properties / episode_number / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / episode_number / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / guest_stars / items / properties / character / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / guest_stars / items / properties / character / type
```
Added value: +[
+  "string",
+  "null"
+]
```

addedOutput schema / properties / imdb_id

Added value: +{
+  "description": "This episode's own IMDb id (not the show's) — pass it to get_ratings for the episode's IMDb rating, which no TMDB field carries. Null when TMDB has no IMDb id for it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / imdb_url

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

removedOutput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / overview / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / overview / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / runtime_minutes / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / runtime_minutes / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / season_number / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / season_number / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / still_url / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / still_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / vote_average / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / vote_average / description

Added value: +"TMDB's own 0-10 user score. A different audience and scale from the IMDb/RT/Metacritic scores get_movie/get_tv return as `ratings` — don't compare, average or substitute across the two."

addedOutput schema / properties / vote_average / type
```
Added value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / required

Previous value: -[
-  "season_number",
-  "episode_number",
-  "name",
-  "air_date",
-  "runtime_minutes",
-  "vote_average",
-  "overview",
-  "still_url",
-  "guest_stars",
-  "crew"
-]New value: +[
+  "season_number",
+  "episode_number",
+  "imdb_id",
+  "imdb_url",
+  "name",
+  "air_date",
+  "runtime_minutes",
+  "vote_average",
+  "overview",
+  "still_url",
+  "guest_stars",
+  "crew"
+]

Changed2 schema fields changedv0.10.1Jul 30, 2026

changedOutput schema / properties / air_date / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date",
+    "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])))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / air_date / default
```
Added value: +null
```

Addedv0.8.1Jul 26, 2026
Removedv0.8.0Jul 22, 2026
First observedv0.3.0Jul 9, 2026

TDQS

A4.6/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 known. The description adds useful behavior beyond annotations: it notes no OMDb call is made, lists guest stars capped at 15, and explains the imdb_id handoff to get_ratings. It does not cover error cases or rate limits, but those are minor given the output schema and openWorldHint.

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 description is front-loaded with the core purpose and every clause (rating clarification, imdb_id handoff, show id source) earns its place for disambiguation. However, it is a dense, parenthetical-heavy run-on that would be easier to parse as separate sentences or bullets.

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?

Given a simple 3-parameter read-only tool with an output schema and annotations, the description covers everything an agent needs: what it returns, how to obtain the show id, and how to get per-episode IMDb ratings via get_ratings. No critical gaps remain.

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 a useful pointer ('Get the show id from search_tv') and reiterates the required id/season/episode combination, but does not expand on the semantics of season_number (0 = specials) or episode_number beyond what the schema already states.

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 ('Get one episode of a TV show') and enumerates returned fields, then explicitly distinguishes itself from get_movie/get_tv (whole-show ratings only) and get_ratings (per-episode IMDb via imdb_id). An agent can identify the exact operation and scope without opening the 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?

Provides explicit routing: 'pass that id to get_ratings for this one episode's IMDb rating' and 'Get the show id from search_tv.' It also clarifies that get_movie/get_tv ratings are whole-show only, which implicitly tells the agent when not to use this tool for aggregate ratings.

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