Skip to main content
Glama
drakonkat

wizzy-mcp-tmdb

movie_images

Fetch movie posters, backdrops, and logos using TMDB ID to support AI image processing and content enrichment with optional language filtering.

Instructions

Fetches images (posters, backdrops, logos) for a movie. Input: movie_id (required TMDB ID), language (optional ISO 639-1 code), include_image_language (optional comma-separated languages). Output: JSON with image arrays. Purpose: Obtain visual media assets for a movie to support AI-driven image processing or content enrichment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_image_languageNoFilter image languages (comma-separated ISO 639-1 codes or 'null')
languageNoISO 639-1 language (e.g., en-US)
movie_idYesTMDB Movie ID

Implementation Reference

  • The handler function for the 'movie_images' tool. It fetches images (posters, backdrops, logos) for the specified movie ID from the TMDB API using the tmdbFetch helper and returns the data as a JSON string in text content format.
    handler: async ({movie_id, language, include_image_language}) => {
        const data = await tmdbFetch(`/movie/${movie_id}/images`, {language, include_image_language});
        return {content: [{type: "text", text: JSON.stringify(data, null, 2)}]};
    }
  • The input schema (JSON Schema) for the 'movie_images' tool, defining required movie_id and optional language and include_image_language parameters.
    inputSchema: {
        type: "object",
        properties: {
            movie_id: {type: "number", description: "TMDB Movie ID"},
            language: {type: "string", description: "ISO 639-1 language (e.g., en-US)"},
            include_image_language: {
                type: "string",
                description: "Filter image languages (comma-separated ISO 639-1 codes or 'null')"
            }
        },
        required: ["movie_id"],
        additionalProperties: false
    },
  • The complete tool object for 'movie_images' defined in the tools array, which is used by the MCP server's ListTools and CallTool request handlers to register and dispatch the tool.
    {
        name: "movie_images",
        description: "Fetches images (posters, backdrops, logos) for a movie. Input: movie_id (required TMDB ID), language (optional ISO 639-1 code), include_image_language (optional comma-separated languages). Output: JSON with image arrays. Purpose: Obtain visual media assets for a movie to support AI-driven image processing or content enrichment.",
        inputSchema: {
            type: "object",
            properties: {
                movie_id: {type: "number", description: "TMDB Movie ID"},
                language: {type: "string", description: "ISO 639-1 language (e.g., en-US)"},
                include_image_language: {
                    type: "string",
                    description: "Filter image languages (comma-separated ISO 639-1 codes or 'null')"
                }
            },
            required: ["movie_id"],
            additionalProperties: false
        },
        handler: async ({movie_id, language, include_image_language}) => {
            const data = await tmdbFetch(`/movie/${movie_id}/images`, {language, include_image_language});
            return {content: [{type: "text", text: JSON.stringify(data, null, 2)}]};
        }
    },
  • The tmdbFetch helper function used by the movie_images handler (and other tools) to make authenticated API requests to the TMDB proxy endpoint.
    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();
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the output format ('JSON with image arrays') and purpose, but lacks details on rate limits, authentication needs, error handling, pagination, or what happens if no images are found. For a read-only tool with no annotation coverage, this leaves significant 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 functionality, followed by input/output details and purpose. It uses three concise sentences with no wasted words, though the purpose sentence could be integrated more smoothly. Overall, it is efficiently structured and appropriately sized.

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 the basic purpose and parameters but lacks depth for a tool with 3 parameters and behavioral unknowns. It does not explain return value structure beyond 'JSON with image arrays', leaving the agent to infer details. For a read-only tool, this is adequate but with clear gaps in behavioral context.

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 adds minimal value by listing parameters in parentheses but does not provide additional context like format examples beyond the schema (e.g., how include_image_language filtering works in practice). Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Fetches images'), resource ('for a movie'), and scope ('posters, backdrops, logos'), distinguishing it from sibling tools like get_tmdb_details or movie_credits by focusing exclusively on visual media assets. The purpose statement further clarifies its use for AI-driven image processing or content enrichment.

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 when visual media assets are needed, but does not explicitly state when to use this tool versus alternatives like get_tmdb_details (which might include some image data) or other movie-related tools. No exclusions or prerequisites are mentioned, leaving usage context somewhat open-ended.

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