Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmdb_search

Search TMDB movies, TV shows, people, and collections by query, with optional type filters and pagination for structured 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 upstream. Credential-free public TMDB data.

Input Schema

TableJSON 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

A4.2/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses the key interleaving behavior for unscoped queries and states that the data is credential-free public TMDB data, telling the agent no auth is needed. It omits result format and pagination details, but those are less critical for a search tool.

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?

Three sentences with no filler. The core action is front-loaded, followed by a useful behavioral nuance and an auth note. Every sentence earns its place.

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?

For a simple search tool with no output schema, the description covers scope, interleaving behavior, and credential-free access. It doesn't describe result fields or pagination, but the schema documents page/limit defaults, and an agent has enough to invoke it correctly.

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 baseline is 3. The description adds meaning by clarifying that an unscoped query interleaves results across all four types, which explains the interaction between the query and type parameters beyond the schema's simple 'Optional result type filter'.

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 action and resource: 'Searches TMDB movies, TV shows, people, and collections.' It clearly identifies the scope and distinguishes itself from single-type siblings like tmdb_movie and tmdb_tv by covering all four types in one search.

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 description explains behavior (interleaving of unscoped queries) but does not explicitly say when to use this tool versus alternatives like tmdb_movie, tmdb_tv, or tmdb_collection. Usage is implied by the multi-type scope, but no exclusions or alternative conditions are named.

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