Skip to main content
Glama
Grinv

TMDB MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get TV cast & crew

get_tv_credits
Read-only

List a TV show's cast and key crew across its full run by TMDB id, ranked by episode count, with main characters and lead jobs like director and writer.

Instructions

List a TV show's cast and key crew across its whole run, by TMDB id: up to 20 cast members ranked by how many episodes they appear in (each with their main character and episode_count), plus up to 5 people per key crew job — Director, Writer, Teleplay, Story, Executive Producer, Producer, Original Music Composer, Director of Photography — ranked by episode_count, so 'who directed most of it' is the first Director listed. Creators aren't listed here; use get_tv's created_by. For one specific episode's director/writer, use get_tv_episode. Get the id from search_tv.

Input Schema

NameRequiredDescriptionDefault
idYesTMDB numeric id.

Output Schema

NameRequiredDescriptionDefault
castYes
crewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.14.0
    • removedOutput schema / properties / cast / items / properties / character / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / cast / items / properties / character / type
      Added value: +[
+  "string",
+  "null"
+]
    • addedOutput schema / properties / cast / items / properties / episode_count
      Added value: +{
+  "description": "Episodes across the whole run this person appears in, in any role.",
+  "type": "number"
+}
    • changedOutput schema / properties / cast / items / required
      Previous value: -[
-  "character"
-]New value: +[
+  "character",
+  "episode_count"
+]
    • addedOutput schema / properties / crew / items / properties / episode_count
      Added value: +{
+  "description": "Episodes across the whole run this person is credited on in this job.",
+  "type": "number"
+}
    • addedOutput schema / properties / crew / items / required
      Added value: +[
+  "job",
+  "episode_count"
+]
  2. Addedv0.8.1
  3. Removedv0.8.0
  4. First observedv0.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), and the description adds substantial non-annotation behavior: result caps (20 cast, 5 per crew job), ranking by episode_count, and the semantic that the first Director is the one who directed most episodes. That is exactly the kind of context annotations cannot express.

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?

Front-loaded with the core purpose and no filler sentences, but the payload is one long run-on sentence with nested clauses that an agent must parse in pieces. Slightly shorter, chunked phrasing would improve scanability.

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 one-parameter read tool with an output schema and full annotation coverage, nothing an agent needs is missing: it knows what comes back, how it is ordered, how it is capped, and where to get the input and the alternatives.

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% and the `id` description already says TMDB numeric id, so the baseline is 3; the description adds marginal value by telling the agent to obtain the id via search_tv, closing the provenance gap. It does not add format constraints 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?

States a specific verb (List) and resource (a TV show's cast and key crew across its whole run), plus the identifier domain (TMDB id). It is clearly distinct from get_movie_credits and from get_tv, so an agent can select it 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?

Explicitly routes the agent: creators live in get_tv's `created_by`, a single episode's director/writer is get_tv_episode, and the id comes from search_tv. Both exclusion and prerequisite are named.

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

Deploy Server

Other Tools