Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmdb_movie_list

Retrieve a paginated TMDB movie chart by category, then filter by genre, language, release date, rating, votes, or runtime to find matching titles.

Instructions

Get a TMDB movie chart. Returns a page of TMDB movies from the category chart (popular by default, or top_rated, now_playing, upcoming), optionally refined by sort_by, with_genres, original_language, release dates, rating, votes and runtime. limit defaults to 10 (max 20). Each movie has id, title, overview, poster, release date and uri; has_next_page signals more pages.

Input 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

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does a fair job: it states the tool is a retrieval operation, discloses pagination via 'has_next_page', and bounds the page size ('limit defaults to 10 (max 20)'). It omits any note on rate limits, caching, or whether results are stable across pages, which keeps it from a 5.

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?

Three tight sentences front-load purpose, then filters, then limits and return shape. Slight redundancy with the schema on the limit default and category default keeps it just below exemplary.

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 optional parameters and no output schema, the description compensates by listing the returned fields (id, title, overview, poster, release date, uri) and the pagination signal, which is exactly what an agent needs to chain calls. A brief disambiguation note versus tmdb_movie/tmdb_search is the only real gap.

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 coverage is 100%, so all 14 parameters are already documented in the schema; the description only restates the category enum, the limit default/max, and groups the filter families. It adds no interpretation the schema lacks (e.g. how sort_by interacts with category, or what with_genres ids mean).

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 opens with a specific verb and resource ('Get a TMDB movie chart. Returns a page of TMDB movies'), enumerates the four chart categories, and makes clear this is a browsable list rather than a detail lookup. It never names the sibling tools (tmdb_movie, tmdb_search, tmdb_tv_list) that an agent would otherwise confuse it with, so sibling differentiation is only implicit.

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 implied rather than stated: the word 'chart' plus the optional refinement filters suggests discovery/browsing when no specific title is known. There is no explicit 'use this when…' or 'use tmdb_search instead when…' statement, which matters given several nearby TMDB tools.

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