Skip to main content
Glama

Get person details

get_person
Read-only

Retrieve a TMDB person's biography, birthday, and known-for titles; append credits, images, or external IDs to build a filmography in one response.

Instructions

Details for a person (actor, director, crew): biography, birthday, known for. Use append for movie_credits, tv_credits or combined_credits to get their filmography.

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": {
      "person_id": "<person_id>"
    },
    "name": "get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
appendNoExtra sections to embed in the same response: movie_credits, tv_credits, combined_credits, images, external_ids, translations
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
person_idYesTMDB person ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context by explaining that append embeds extra sections 'in the same response', telling the agent it saves a round trip, and it previews the returned content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is returned and followed by the one non-obvious parameter tip. Nothing is redundant with the schema or the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with full schema coverage and no output schema, the definition covers resource, returned fields, and the extension mechanism. Only the absence of guidance on where person_id comes from keeps it short of complete.

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%, so all three parameters, including the append enum and language fallback to TMDB_LANGUAGE, are already documented. The description adds only the purpose framing for three of the six append values, which is marginal value over the schema — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource ('Details for a person') and enumerates the returned fields (biography, birthday, known for), which is more than a restatement of the title. It is clearly the person-lookup tool relative to get_movie/get_tv_show siblings, though it never explicitly names an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is parameter-directed: use append for movie_credits/tv_credits/combined_credits to obtain a filmography. That implies the tool is the entry point for person data, but there is no statement of when to prefer a search tool first or how to obtain the required person_id.

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