Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmdb_person

Retrieve a TMDB person by ID to get their biography, birth date, photo, and top movie and TV credits. Use the optional limit to cap filmography results.

Instructions

Get a TMDB person. Returns a TMDB person by id: name, biography, birth date, photo URL and a filmography of movie and TV credits, most prominent first. limit caps the credits (default 10, max 20). Each credit has its type (movie or tv), id, title and uri. The biography may include a Wikipedia CC-BY-SA attribution note.

Input Schema

NameRequiredDescriptionDefault
idYesTMDB person id
limitNoMax filmography credits, default 10, max 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses the credit cap semantics (default 10, max 20), the sort order ('most prominent first'), the per-credit shape (`type` movie/tv, id, title, uri) and a Wikipedia CC-BY-SA attribution note in the biography. It does not mention rate limits, invalid-id behavior, or that this is a non-mutating read, but the payload disclosure is unusually thorough.

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?

Four short sentences, each carrying distinct information: identity, payload fields, the limit parameter, and credit structure plus attribution. Nothing is redundant and the essential retrieval fact (returns by id) is front-loaded.

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?

There is no output schema, so the return-value description is doing necessary work and covers fields, credit shape and cap behavior. The only gaps are operational: how to obtain a valid person id and what happens on an unknown id.

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 the baseline is 3. The description largely restates the schema ('limit caps the credits (default 10, max 20)') and adds only the ordering nuance ('most prominent first') that explains what the cap selects; `id` is not elaborated beyond 'by `id`'.

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 specific verb and resource ('Get a TMDB person') and then enumerates the payload (name, biography, birth date, photo URL, filmography of movie and TV credits), which clearly separates it from tmdb_movie, tmdb_tv and tmdb_collection. It never explicitly names a sibling to route away from, so it is clear but not fully differentiating.

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?

Usage is only implied: the agent must already hold a TMDB person `id`, and the description never says where that id comes from (e.g. tmdb_search or tmdb_person_list) or when to prefer this over those tools. No exclusions or prerequisites are stated, so the agent has to infer the call condition.

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