Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmdb_movie_list

Fetch TMDB movie charts including popular, top-rated, now playing, or upcoming movies with filtering by genre, rating, runtime, and release date. Returns clean JSON data without requiring credentials.

Instructions

Get a TMDB movie chart. Returns a TMDB movie chart (popular, top rated, now playing, or upcoming). Credential-free public TMDB data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, default 1
limitNoMax movies, default 10, max 20
date_toNoRelease date upper bound (YYYY-MM-DD)
sort_byNoSort order
categoryNoMovie chart, default popular
date_fromNoRelease date lower bound (YYYY-MM-DD)
min_votesNoMinimum vote count
max_ratingNoMaximum rating, 0-10
min_ratingNoMinimum rating, 0-10
max_runtimeNoMaximum runtime in minutes
min_runtimeNoMinimum runtime in minutes
with_genresNoComma- or pipe-separated movie genre ids: 28,12,16,35,80,99,18,10751,14,36,27,10402,9648,10749,878,10770,53,10752,37
include_adultNoInclude adult titles
original_languageNoTwo-letter original-language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / category / enum
      Added value: +[
+  "popular",
+  "top_rated",
+  "now_playing",
+  "upcoming"
+]
    • addedInput schema / properties / sort_by / enum
      Added value: +[
+  "popularity.desc",
+  "popularity.asc",
+  "vote_average.desc",
+  "vote_average.asc",
+  "primary_release_date.desc",
+  "primary_release_date.asc",
+  "title.asc",
+  "title.desc"
+]
    • changedInput schema / properties / with_genres / description
      Previous value: -"Comma- or pipe-separated TMDB genre ids"New value: +"Comma- or pipe-separated movie genre ids: 28,12,16,35,80,99,18,10751,14,36,27,10402,9648,10749,878,10770,53,10752,37"
  2. Changed12 schema fields changed
    • addedInput schema / properties / date_from
      Added value: +{
+  "description": "Release date lower bound (YYYY-MM-DD)",
+  "type": "string"
+}
    • addedInput schema / properties / date_to
      Added value: +{
+  "description": "Release date upper bound (YYYY-MM-DD)",
+  "type": "string"
+}
    • addedInput schema / properties / include_adult
      Added value: +{
+  "description": "Include adult titles",
+  "type": "boolean"
+}
    • addedInput schema / properties / max_rating
      Added value: +{
+  "description": "Maximum rating, 0-10",
+  "type": "number"
+}
    • addedInput schema / properties / max_runtime
      Added value: +{
+  "description": "Maximum runtime in minutes",
+  "type": "integer"
+}
    • addedInput schema / properties / min_rating
      Added value: +{
+  "description": "Minimum rating, 0-10",
+  "type": "number"
+}
    • addedInput schema / properties / min_runtime
      Added value: +{
+  "description": "Minimum runtime in minutes",
+  "type": "integer"
+}
    • addedInput schema / properties / min_votes
      Added value: +{
+  "description": "Minimum vote count",
+  "type": "integer"
+}
    • addedInput schema / properties / original_language
      Added value: +{
+  "description": "Two-letter original-language code",
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-based page, default 1",
+  "type": "integer"
+}
    • addedInput schema / properties / sort_by
      Added value: +{
+  "description": "Sort order",
+  "type": "string"
+}
    • addedInput schema / properties / with_genres
      Added value: +{
+  "description": "Comma- or pipe-separated TMDB genre ids",
+  "type": "string"
+}
  3. Addedv1.5.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses that the data is credential-free and public, which is useful, but it does not describe output shape, pagination behavior, how filters interact with categories, or any rate-limit expectations. For a 14-parameter tool, this is a notable gap.

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

Conciseness3/5

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

The description is short and front-loaded, but it is redundant: 'Get a TMDB movie chart' and 'Returns a TMDB movie chart' say essentially the same thing. It could be tightened to a single sentence without losing information.

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

Completeness2/5

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

With 14 parameters, no output schema, and no annotations, the description is too thin. It does not explain what the returned chart looks like, how the many filters combine, or what the default behavior is beyond schema-level defaults. An agent would need to inspect the schema carefully and still lacks return-format context.

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%, with each of the 14 parameters documented. The description itself adds no parameter-level meaning beyond reiterating the category names that already appear in the enum, so the schema carries the load and the baseline of 3 applies.

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?

The description clearly identifies the resource (TMDB movie chart) and enumerates the chart categories (popular, top rated, now playing, upcoming), which distinguishes it from siblings like tmdb_movie (single movie), tmdb_tv_list (TV chart), and tmdb_search (search). It does not explicitly name these siblings, but the resource-and-verb combination is sufficiently specific.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as tmdb_search, tmdb_movie, or tmdb_tv_list. The chart categories imply use cases, but no explicit when/when-not or alternative routing is given.

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