Crawlora MCP

tmdb_movie_list

Read-only

Fetch one page of a TMDB movie chart such as popular, top-rated, now-playing, or upcoming. Use tmdb_search for a title query, tmdb_movie for one movie's details, or tmdb_tv_list for TV charts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tmdb_movie_list"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page, default 1.
`limit`	No	Max movies, default 10, max 20.
`date_to`	No	Release/first-air date upper bound, YYYY-MM-DD.
`sort_by`	No	Sort order; allowed values depend on movie vs TV.
`category`	No	Movie chart, default popular.
`date_from`	No	Release/first-air date lower bound, YYYY-MM-DD.
`min_votes`	No	Minimum vote count.
`max_rating`	No	Maximum TMDB user rating, 0-10.
`min_rating`	No	Minimum TMDB user rating, 0-10.
`max_runtime`	No	Maximum runtime in minutes.
`min_runtime`	No	Minimum runtime in minutes.
`with_genres`	No	Comma- or pipe-separated TMDB genre ids.
`include_adult`	No	Include adult titles.
`original_language`	No	Two-letter original-language code.

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.4/5.0

Behavior3/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 without the description. The description adds only the 'one page' scope note, which is useful but largely echoed by the page parameter in the schema; it says nothing about rate limits, auth, or result shape beyond the pagination scope.

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 the scoping verb and resource, then the routing guidance. No wasted words and no restatement of 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?

With 14 params fully described in the schema, an output schema present, and annotations carrying the safety profile, the description supplies the essential routing and chart-scope context. It is complete enough for correct invocation; minor gaps like listing all valid category/sort_by values are appropriately left to the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all 14 parameters, giving a baseline of 3. The description adds value by naming concrete category values (popular, top-rated, now-playing, upcoming) that the schema's category field does not enumerate, clarifying what the chart filter means in practice.

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 ('Fetch one page of a TMDB movie chart') and enumerates the chart variants (popular, top-rated, now-playing, upcoming), which is more precise than the bare title. It explicitly names the sibling tools it is not, so an agent can distinguish it from tmdb_search, tmdb_movie, and tmdb_tv_list without opening any schema.

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?

Goes beyond naming alternatives by pairing each with the condition that selects it: tmdb_search for a title query, tmdb_movie for one movie's details, tmdb_tv_list for TV charts. This gives explicit routing among the closest siblings, leaving nothing to inference.

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?