Skip to main content
Glama
TMDB MCP Server

TMDB MCP Server

Get person filmography

get_person_credits
Read-only

List the movies and TV shows a person is known for, with cast and crew credits ranked by popularity and optional department filtering to isolate roles like directing.

Instructions

List the movies and TV shows a person is known for (cast roles and crew jobs; adult/softcore titles left out), most popular first, capped to the top 25 of each by default. Talk-show/awards-show guest appearances ('Self'/'Himself'/'Herself', plus any cast credit on a TV talk or news show) and repeat entries for the same title are excluded so the list stays about actual roles. A cameo credited under the person's own name is kept, since TMDB marks it no differently from a real role (checked live: Tom Hanks's top cast row is The Simpsons as 'Tom Hanks (voice)'). A title with several crew jobs (writer AND director AND producer on one film) counts once against the crew cap. Cast entries include a vote_average; crew entries (director, writer, …) do not, so call get_movie/get_tv on the id for a crew credit's own vote_average. Pass department (e.g. 'Directing') to restrict crew to just that role: the reliable way to get someone's complete filmography in one department when their other departments would compete for the same cap. For a handful of very prolific people even that isn't enough (e.g. 50+ directing credits), so raise limit too when department alone still looks short. Use for 'what has this actor/director been in'. This tool has no genre filter; for 'which of X's movies are animated/horror/etc.' use discover_movies, combining with_cast/with_crew/with_people with with_genres. discover_tv can't filter by person at all, so for a person's TV work in one genre, call this tool and check the returned media_type 'tv' entries' genres yourself, e.g. via get_tv_shows. Get the id from search_people.

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_person_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTMDB person id (from search_people).
limitNoMax cast entries and max crew entries to return (each capped separately, 1-100). Raise this for a very prolific person (e.g. a director with 50+ films) when even a department filter leaves more titles than the default cap keeps.
departmentNoRestrict crew credits to this department (e.g. 'Directing' for a director's filmography). Without it, a multi-hyphenate's other departments (writing, producing, ...) compete for the same 25-credit cap and can crowd out the department you want.

Output Schema

NameRequiredDescriptionDefault
castYes
crewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.15.0
    • changedInput schema / properties / department / description
      Previous value: -"Restrict crew credits to this department (e.g. 'Directing' for a director's filmography). Without it, a multi-hyphenate's OTHER departments (writing, producing, …) compete for the same 25-credit cap and can crowd out titles in the department you actually want."New value: +"Restrict crew credits to this department (e.g. 'Directing' for a director's filmography). Without it, a multi-hyphenate's other departments (writing, producing, ...) compete for the same 25-credit cap and can crowd out the department you want."
    • changedInput schema / properties / id / description
      Previous value: -"TMDB numeric id."New value: +"TMDB person id (from search_people)."
    • addedInput schema / properties / limit / default
      Added value: +25
    • changedInput schema / properties / limit / description
      Previous value: -"Max cast entries and max crew entries to return (each capped separately; default 25). Raise this for an exceptionally prolific person — e.g. a director with 50+ films — where even a department filter still leaves more titles than the default cap keeps."New value: +"Max cast entries and max crew entries to return (each capped separately, 1-100). Raise this for a very prolific person (e.g. a director with 50+ films) when even a department filter leaves more titles than the default cap keeps."
  2. Changed13 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"
      +]
    • removedOutput schema / properties / cast / items / properties / vote_average / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / cast / items / 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 / cast / items / properties / vote_average / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / cast / items / properties / year / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / cast / items / properties / year / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / crew / items / properties / department / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / crew / items / properties / department / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / crew / items / properties / job / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / crew / items / properties / job / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / crew / items / properties / year / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / crew / items / properties / year / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  3. Addedv0.8.1
  4. Removedv0.8.0
  5. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Discloses many behaviors beyond the readOnly/openWorld annotations: exclusions for adult titles, talk shows, awards shows, and repeat entries; cameo handling; crew-job deduplication; vote_average differences between cast and crew; and cap behavior. These details materially help an agent predict results and avoid misuse.

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?

Information is front-loaded and mostly earns its place, moving from purpose to exclusions to parameter behavior to alternatives. It is longer than necessary in places, with parenthetical examples such as the Tom Hanks cameo and detailed genre workarounds, but the structure remains usable.

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 the tool's complexity and the existence of an output schema, the description is complete enough for correct invocation. It covers sorting, caps, exclusions, crew-vs-cast differences, department filtering, limit escalation, and alternative tools for genre-specific queries.

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%, and the schema already documents id, limit, and department thoroughly. The description largely restates the department/limit interaction rather than adding substantially new parameter meaning, so the high-coverage baseline applies.

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: lists a person's movies and TV shows, including cast and crew credits, sorted by popularity and capped by default. It clearly distinguishes this from genre/person search tools and says what the output represents.

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?

Gives explicit when-to-use guidance ('what has this actor/director been in') and concrete alternatives for genre-filtered person queries using discover_movies, while noting discover_tv cannot filter by person. It also tells the agent to get the id from search_people.

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