Skip to main content
Glama

Search TMDB

search
Read-only

Find TMDB movies, TV shows, and people by text, or narrow to a type, and return paged results with IDs for other tools.

Instructions

Search TMDB by text. type=multi (default) searches movies, TV shows and people together; pick a specific type to narrow it. Returns paged results with the IDs the other tools take.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResults page, 1-500. Each page holds up to 20 results.
typeNoWhat to searchmulti
yearNoFilter by release year (type=movie) or first air date year (type=tv). Ignored for other types.
queryYesText to search for
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
include_adultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint and openWorldHint already cover the safety profile, and the description adds real context beyond them: results are paged and the returned IDs are the ones the other tools accept, which is a key chaining fact. It says nothing about adult-content filtering (the include_adult parameter) or result caps, but the added handoff information is genuinely valuable.

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 compact sentences with zero filler, front-loaded with the core action and scope, then the type-narrowing rule and a note on returns. Every clause 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?

With no output schema, the description correctly compensates by stating that results are paged and carry the IDs used by other tools. Only minor gaps remain, such as the undocumented include_adult parameter, which is not explained in the schema either.

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 83%, so the baseline is 3, but the description improves on the schema's vague type description ("What to search") by explaining that multi combines movies, TV and people while a specific value narrows it. It also implies the paging behavior tied to the page parameter, adding meaning the schema does not spell out.

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 ("Search TMDB by text") and immediately explains the default multi-search scope, so the agent knows exactly what the tool does. It stops short of naming a sibling it is not (e.g. discover_movies or find_by_external_id), which keeps it from a 5.

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?

It gives useful in-tool guidance: multi is the default and a specific type narrows the search. But it never addresses tool selection — nothing tells the agent when to prefer this over discover_movies, get_trending, or find_by_external_id, so the when-to-use-vs-alternatives dimension is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.