Skip to main content
Glama
drakonkat

wizzy-mcp-tmdb

trending_movies

Discover currently popular movies by retrieving trending titles from The Movie Database for daily or weekly trend analysis.

Instructions

Retrieves trending movies. Input: time_window (required: day|week), page (optional), language (optional ISO 639-1), region (optional ISO 3166-1), include_adult (optional boolean). Output: JSON with paginated trending results. Purpose: Discover currently popular movies for trend analysis by AI agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_adultNo
languageNo
pageNo
regionNo
time_windowYes

Implementation Reference

  • The main handler function for the 'trending_movies' tool. It calls the TMDB API endpoint `/trending/movie/${time_window}` with provided parameters, fetches the data, stringifies it to JSON, and returns it as text content in the MCP response format.
    handler: async ({time_window, page, language, region, include_adult}) => {
        const data = await tmdbFetch(`/trending/movie/${time_window}`, {page, language, region, include_adult});
        return {content: [{type: 'text', text: JSON.stringify(data, null, 2)}]};
    }
  • The input schema defining the parameters for the 'trending_movies' tool: required 'time_window' ("day" or "week"), optional 'page', 'language', 'region', 'include_adult'.
    inputSchema: {
        type: "object",
        properties: {
            time_window: {type: "string", enum: ["day", "week"]},
            page: {type: "number", minimum: 1},
            language: {type: "string"},
            region: {type: "string"},
            include_adult: {type: "boolean"}
        },
        required: ["time_window"],
        additionalProperties: false
    },
  • The tool registration object added to the 'tools' array, which includes name, description, inputSchema, and handler. This array is used by the MCP server to list and dispatch tools via ListToolsRequest and CallToolRequest handlers.
    {
        name: "trending_movies",
        description: "Retrieves trending movies. Input: time_window (required: day|week), page (optional), language (optional ISO 639-1), region (optional ISO 3166-1), include_adult (optional boolean). Output: JSON with paginated trending results. Purpose: Discover currently popular movies for trend analysis by AI agents.",
        inputSchema: {
            type: "object",
            properties: {
                time_window: {type: "string", enum: ["day", "week"]},
                page: {type: "number", minimum: 1},
                language: {type: "string"},
                region: {type: "string"},
                include_adult: {type: "boolean"}
            },
            required: ["time_window"],
            additionalProperties: false
        },
        handler: async ({time_window, page, language, region, include_adult}) => {
            const data = await tmdbFetch(`/trending/movie/${time_window}`, {page, language, region, include_adult});
            return {content: [{type: 'text', text: JSON.stringify(data, null, 2)}]};
        }
    },
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses that output is 'JSON with paginated trending results,' adding useful context beyond basic retrieval, but lacks details on rate limits, authentication needs, or error handling, leaving behavioral gaps.

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?

The description is front-loaded with the core purpose, followed by parameter details and output, with no wasted sentences. It could be slightly more structured but remains efficient and clear.

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?

Given no annotations and no output schema, the description covers purpose, parameters, and output format adequately for a retrieval tool, but lacks details on pagination behavior, error cases, or integration with siblings, leaving room for improvement.

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 description coverage is 0%, so the description must compensate. It lists all 5 parameters with brief semantics (e.g., 'time_window (required: day|week)'), adding meaning beyond the bare schema, though it could elaborate on defaults or effects.

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 verb ('Retrieves') and resource ('trending movies'), and distinguishes from siblings by specifying 'for trend analysis by AI agents' and focusing on current popularity, unlike discovery or search tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage for 'currently popular movies for trend analysis,' which gives context, but does not explicitly state when to use this vs. alternatives like trending_all, trending_tv, or discover_movies, missing explicit exclusions or comparisons.

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/drakonkat/wizzy-mcp-tmdb'

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