Skip to main content
Glama
Grinv

TMDB MCP Server

Get person filmography

get_person_credits
Read-only

Retrieve a person's known movie and TV show credits, including cast roles and crew jobs, while excluding talk-show appearances and duplicates. Optionally filter by department and raise the limit for extensive filmographies.

Instructions

List the movies and TV shows a person is known for (cast roles and crew jobs), most popular first, capped to the top 25 of each by default; talk-show/awards-show guest appearances ('Self'/'Himself'/'Herself') and repeat entries for the same title are excluded so the list stays about actual roles. A title with several crew jobs (writer AND director AND producer on one film) still only counts once against the crew cap. Cast entries include a vote_average; crew entries (director, writer, …) do not — call get_movie/get_tv on the id for a crew credit's rating. 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 otherwise compete for the same cap; for a handful of exceptionally 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 instead, combining with_cast/with_crew/with_people with with_genres (discover_tv has no equivalent — it 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTMDB numeric id.
limitNoMax 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.
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 titles in the department you actually want.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
castYes
crewYes
Behavior5/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. Description adds details: default cap of 25, exclusion of talk-show appearances and duplicates, deduplication of multiple crew jobs, cast entries include vote_average but crew do not, and behavior of department and limit parameters for prolific people.

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?

Long but every sentence adds valuable information. Front-loaded with main purpose. Could be slightly more concise, but efficient given the complexity.

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?

Completeness is high: covers purpose, parameters, limitations, alternatives, and output details (e.g., cast vs crew attributes). Output schema exists but description still provides behavioral context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but description adds significant value beyond schema: explains why raise limit for prolific people, why use department to avoid crowding, that department only affects crew credits, and that without department, other departments compete for cap.

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?

Clearly states the tool lists movies and TV shows a person is known for, with cast and crew roles, most popular first, capped at 25 each. Differentiates from sibling tools like search_people, get_movie_credits, and discover_movies by specifying its focus on a person's combined filmography and exclusion of guest appearances.

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 tells when to use: 'for what has this actor/director been in'. Provides alternatives: use discover_movies with with_cast/with_crew/with_people for genre filtering, and for TV genres, call this tool then check media_type. Says to get 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/tmdb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server