Skip to main content
Glama
TMDB MCP Server

TMDB MCP Server

Get TV cast & crew

get_tv_credits
Read-only

List a TV show's full-run cast and key crew by TMDB ID, ranked by episode count, to identify main characters and frequent directors.

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.

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": {
      "id": "<id>"
    },
    "name": "get_tv_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTMDB TV show id (from search_tv).

Output Schema

NameRequiredDescriptionDefault
castYes
crewYes

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 TV show id (from search_tv)."
  2. 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"
      +]
  3. Addedv0.8.1
  4. Removedv0.8.0
  5. First observedv0.3.0

TDQS

A4.4/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 goes further by disclosing result caps (20 cast, 5 per crew job), the ranking/ordering rule, and the guarantee that 'who directed most of it' appears first, which is real behavioral context. It stops short of mentioning pagination or what happens for shows with sparse credits.

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 action and scope, and the alternative-tool routing is pushed to the end where it belongs. The middle sentence is dense with enumerated crew jobs and parenthetical asides, slightly taxing, but each clause carries information an agent would otherwise have to discover.

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 still sketches the return shape (character, episode_count, ordering) in a way that helps the agent reason about results. For a one-parameter read tool with full schema coverage and annotations, nothing needed for correct invocation is missing.

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 coverage is 100% and the single `id` parameter is already documented as 'TMDB TV show id (from search_tv)'. The description repeats the same provenance hint ('by TMDB id', 'Get the id from search_tv') without adding format or constraint detail, so 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?

States a specific verb and resource ('List a TV show's cast and key crew'), then narrows the scope precisely: whole-run, up to 20 cast ranked by episode_count, up to 5 per key crew job, with the job list named. An agent can distinguish it from get_movie_credits, get_person_credits, and get_tv_episode from the text alone.

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 away from this tool in two cases: creators belong to get_tv's `created_by`, and a single episode's director/writer belongs to get_tv_episode. It also states the prerequisite for the id ('Get the id from search_tv'), which is the exact chaining an agent needs.

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