Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmdb_search

Search TMDB for movies, TV shows, people, and collections, with optional type filtering to return mixed or targeted results.

Instructions

Search TMDB. Searches TMDB movies, TV shows, people, and collections. An unscoped query interleaves results across all four types rather than returning whichever type happens to rank first.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page, default 1
typeNoOptional result type filter
limitNoMax results, default 10, max 20
queryYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "movie",
+  "tv",
+  "person",
+  "collection"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-based results page, default 1",
+  "type": "integer"
+}
  3. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one genuine trait beyond the schema: unscoped queries interleave results across the four types rather than returning one dominant type. It omits result ordering guarantees, total-count behavior, and nothing about rate limits or partial-result failure modes.

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 compact sentences with the core purpose front-loaded and no filler. The third sentence earns its place by explaining interleaving behavior, though restating 'Search TMDB' before 'Searches TMDB movies...' is slightly redundant.

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

Completeness3/5

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

No output schema exists, so return values need not be described, and all four params are covered by the schema. What is missing is routing context against the many tmdb_* siblings (e.g., when to use this instead of tmdb_movie/tmdb_tv), which matters for a generic search entry point in a dense tool family.

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 the schema already documents query, type, page, and limit (including the max 20). The description's scoped/unscoped discussion adds conceptual meaning to the `type` enum, but no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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 (search TMDB) and enumerates the four result domains (movies, TV shows, people, collections), which no sibling description states. It does not explicitly name the type-specific siblings (tmdb_movie, tmdb_tv, tmdb_person, tmdb_collection), so differentiation is implied rather than stated.

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?

The note that an unscoped query interleaves all four types implicitly tells the agent when to use this tool (cross-type discovery). However, it never says when to prefer tmdb_movie/tmdb_tv/tmdb_person by ID, nor any exclusions or prerequisites, leaving the routing decision to inference.

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