Crawlora MCP

tmdb_person

Read-only

Returns a normalized TMDB person: biography, birth date, photo, and filmography (movie and TV credits). Credential-free public TMDB data. limit: Max filmography credits, default 10, max 20. id: TMDB person id, e.g. 31. Use tmdb_person_list to list popular people on TMDB.

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>",
      "limit": "<limit>"
    },
    "name": "tmdb_person"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	TMDB person id, e.g. 31.
`limit`	Yes	Max filmography credits, default 10, max 20.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already carry the read-only/open-world profile, so the description's job is lighter. It adds a useful behavioral fact: the data is credential-free public TMDB data, telling the agent no auth is needed. It does not quantify rate limits or note bounded result behavior, but with annotations and an output schema present this is a reasonable add.

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 purpose and payload before the routing hint and parameter notes. The parameter sentences duplicate the schema, which is mild redundancy, but nothing is padded or misleading.

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?

An output schema exists, so return values need not be re-described, and the description still sketches the payload. With both params required and fully documented, and read-only behavior covered by annotations, the definition is complete enough to invoke correctly, missing only explicit id-sourcing guidance.

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 schema already documents both id and limit. The description's 'id: TMDB person id, e.g. 31' and 'limit: Max filmography credits, default 10, max 20' simply restate the schema fields verbatim, adding no syntax or semantic value beyond it. Baseline 3 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 (Returns) and resource (TMDB person) and enumerates the concrete payload: biography, birth date, photo, and filmography. It also names the sibling tmdb_person_list, so an agent can distinguish it from the list-oriented tool without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes to tmdb_person_list when the goal is listing popular people, which clarifies this tool's role as a by-id lookup. However it never states the inverse condition (that you need a known TMDB person id) explicitly, and gives no exclusions.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?