Skip to main content
Glama
drakonkat

wizzy-mcp-tmdb

movie_lists

Find curated collections and lists that include specific movies to support content curation and discovery workflows.

Instructions

Retrieves lists and collections that include a specific movie. Input: movie_id (required TMDB ID), language (optional ISO 639-1 code), page (optional page number). Output: JSON with paginated results of lists containing the movie. Purpose: Discover curated collections and lists featuring a movie for content curation by AI agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoISO 639-1 language (e.g., en-US)
movie_idYesTMDB Movie ID
pageNoPage number

Implementation Reference

  • The handler function implementing the tool logic: fetches lists containing the specified movie from TMDB and returns the data as formatted JSON text.
    handler: async ({movie_id, language, page}) => {
        const data = await tmdbFetch(`/movie/${movie_id}/lists`, {language, page});
        return {content: [{type: "text", text: JSON.stringify(data, null, 2)}]};
    }
  • Input schema for validating tool arguments: requires movie_id (TMDB Movie ID), optional language and page.
    inputSchema: {
        type: "object",
        properties: {
            movie_id: {type: "number", description: "TMDB Movie ID"},
            language: {type: "string", description: "ISO 639-1 language (e.g., en-US)"},
            page: {type: "number", minimum: 1, description: "Page number"}
        },
        required: ["movie_id"],
        additionalProperties: false
    },
  • The tool registration object added to the 'tools' array, which is used by the MCP server's listTools and callTool request handlers.
    {
        name: "movie_lists",
        description: "Retrieves lists and collections that include a specific movie. Input: movie_id (required TMDB ID), language (optional ISO 639-1 code), page (optional page number). Output: JSON with paginated results of lists containing the movie. Purpose: Discover curated collections and lists featuring a movie for content curation by AI agents.",
        inputSchema: {
            type: "object",
            properties: {
                movie_id: {type: "number", description: "TMDB Movie ID"},
                language: {type: "string", description: "ISO 639-1 language (e.g., en-US)"},
                page: {type: "number", minimum: 1, description: "Page number"}
            },
            required: ["movie_id"],
            additionalProperties: false
        },
        handler: async ({movie_id, language, page}) => {
            const data = await tmdbFetch(`/movie/${movie_id}/lists`, {language, page});
            return {content: [{type: "text", text: JSON.stringify(data, null, 2)}]};
        }
    },
  • Helper function used by the handler to perform authenticated API requests to TMDB.
    async function tmdbFetch(path, params = {}) {
        if (!TMDB_AUTH_TOKEN) {
            throw new Error("TMDB authorization token is not configured");
        }
        const url = new URL(TMDB_BASE + path);
        Object.entries(params).forEach(([k, v]) => {
            if (v !== undefined && v !== null && v !== "") url.searchParams.set(k, String(v));
        });
    
        const res = await fetch(url, {
            headers: {
                Accept: "application/json",
                Authorization: TMDB_AUTH_TOKEN,
            },
        });
        if (!res.ok) {
            const text = await res.text().catch(() => "");
            throw new Error(`TMDB request failed ${res.status}: ${text}`);
        }
        return res.json();
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination and output format ('JSON with paginated results'), which is helpful, but lacks details on rate limits, authentication needs, error handling, or what specific data the lists contain. It adequately describes the core behavior but misses deeper operational context.

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 input/output details and a purpose statement. It is appropriately sized with no redundant sentences, though the purpose statement at the end could be integrated more seamlessly for better flow.

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 provides basic operational info (purpose, parameters, output format) but lacks completeness for a tool with 3 parameters and paginated results. It does not explain the structure of the returned lists, error cases, or advanced usage scenarios, leaving gaps for an AI agent to fully understand the tool's behavior.

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 thoroughly. The description lists the parameters and adds that movie_id is a 'required TMDB ID', but this repeats schema info. It provides no additional semantic context beyond what the schema offers, such as examples or constraints not 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's purpose with specific verbs ('Retrieves lists and collections') and resource ('that include a specific movie'), distinguishing it from siblings like discover_movies or search_tmdb_movies which focus on broader discovery or search functions rather than curated lists for a specific movie.

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 context ('for content curation by AI agents') and mentions pagination, but it does not explicitly state when to use this tool versus alternatives like search_tmdb or discover_by_provider, nor does it provide exclusions or prerequisites for usage.

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