Skip to main content
Glama

Discover Movies & TV

tmdb.movies.discover
Read-onlyIdempotent

Discover movies or TV shows by filtering on genre, year, rating, language, and sort order using TMDB data.

Instructions

Discover movies or TV shows by genre, year, rating, language, and sort order (TMDB)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoContent type to discover: "movie" or "tv" (default "movie")
languageNoISO 639-1 language code (e.g. "en-US"). Default: en-US
pageNoPage number (1-500, default 1)
sort_byNoSort field (e.g. "popularity.desc", "vote_average.desc", "revenue.desc", "primary_release_date.desc")
with_genresNoComma-separated genre IDs to filter (e.g. "28,12" for Action+Adventure)
yearNoFilter by release year (movies only)
primary_release_yearNoFilter by primary release year (movies only)
first_air_date_yearNoFilter by first air date year (TV only)
vote_average_gteNoMinimum vote average (0-10)
vote_average_lteNoMaximum vote average (0-10)
with_original_languageNoISO 639-1 original language filter (e.g. "en", "ko", "ja")
regionNoISO 3166-1 region for release dates (e.g. "US", "GB")
include_adultNoInclude adult content (default false)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and other safety traits. The description adds minimal behavioral context beyond what is in the schema, such as noting sort order is from TMDB. No contradictions with annotations.

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?

A single 15-word sentence that immediately conveys the tool's purpose. No redundant information, well front-loaded.

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

Completeness5/5

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

Given the extensive input schema (13 parameters all documented), good annotations, and existence of an output schema, the description provides sufficient context to use this discovery tool effectively. No missing essential information.

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%, so the schema already documents all parameters. The description does not add new meaning or context beyond naming the filter dimensions (genre, year, etc.), which are already in the schema.

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?

The description clearly states the tool discovers movies or TV shows by genre, year, rating, language, and sort order. It uses a specific verb ('Discover') and resource ('movies or TV shows'), distinguishing it from sibling tools like tmdb.movies.search or tmdb.movies.trending.

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 implies usage for discovery/filtering but does not explicitly state when to use this tool versus alternatives (e.g., search, trending). No when-not-to-use or prerequisite information is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server