Skip to main content
Glama
drakonkat

wizzy-mcp-tmdb

get_tmdb_details

Fetch detailed metadata for movies, TV shows, or people using TMDB IDs to support content analysis and information retrieval.

Instructions

Fetches detailed information for a movie, TV show, or person by type and ID. Input: type (required: movie|tv|person), id (required TMDB ID), language (optional ISO 639-1), append (optional comma-separated fields like credits,images). Output: JSON with full item details. Purpose: Obtain in-depth metadata for targeted content analysis by AI agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appendNoComma-separated append_to_response (e.g., credits,images)
idYesTMDB ID
languageNoISO 639-1 code (e.g., en-US)
typeYesThe TMDB media type

Implementation Reference

  • The core handler function that implements the tool logic: fetches TMDB details for specified type and ID using tmdbFetch, supports optional language and append_to_response, formats response as MCP content.
    handler: async ({type, id, language, append}) => {
        const data = await tmdbFetch(`/${type}/${id}`, {language, append_to_response: append});
        return {content: [{type: "text", text: JSON.stringify(data)}]};
    },
  • JSON Schema for tool input validation, defining required 'type' (movie/tv/person) and 'id', optional 'language' and 'append'.
    inputSchema: {
        type: "object",
        properties: {
            type: {type: "string", enum: ["movie", "tv", "person"], description: "The TMDB media type"},
            id: {type: "number", description: "TMDB ID"},
            language: {type: "string", description: "ISO 639-1 code (e.g., en-US)"},
            append: {type: "string", description: "Comma-separated append_to_response (e.g., credits,images)"},
        },
        required: ["type", "id"],
        additionalProperties: false,
    },
  • The tool definition object registered in the 'tools' array, which is used by MCP server handlers for list_tools and call_tool requests.
    {
        name: "get_tmdb_details",
        description: "Fetches detailed information for a movie, TV show, or person by type and ID. Input: type (required: movie|tv|person), id (required TMDB ID), language (optional ISO 639-1), append (optional comma-separated fields like credits,images). Output: JSON with full item details. Purpose: Obtain in-depth metadata for targeted content analysis by AI agents.",
        inputSchema: {
            type: "object",
            properties: {
                type: {type: "string", enum: ["movie", "tv", "person"], description: "The TMDB media type"},
                id: {type: "number", description: "TMDB ID"},
                language: {type: "string", description: "ISO 639-1 code (e.g., en-US)"},
                append: {type: "string", description: "Comma-separated append_to_response (e.g., credits,images)"},
            },
            required: ["type", "id"],
            additionalProperties: false,
        },
        handler: async ({type, id, language, append}) => {
            const data = await tmdbFetch(`/${type}/${id}`, {language, append_to_response: append});
            return {content: [{type: "text", text: JSON.stringify(data)}]};
        },
    },
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 states this is a fetch/read operation (implied safe) and describes the output format (JSON with full item details), which is helpful. However, it doesn't mention rate limits, authentication requirements, error conditions, or pagination behavior that would be valuable for an AI agent.

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?

The description is efficiently structured with three sentences: first states the core function, second lists parameters, third states purpose. Every sentence adds value with no wasted words, and it's appropriately sized for a tool with 4 parameters and no annotations.

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?

For a read-only tool with 100% schema coverage but no output schema, the description provides adequate context by specifying the output format and purpose. However, without annotations or output schema, it could benefit from more behavioral details about error handling or response structure. The description compensates reasonably well given the tool's complexity.

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 restating the parameter names and basic constraints (e.g., 'optional comma-separated fields like credits,images'), but doesn't provide additional semantic context beyond what's in the schema descriptions.

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 ('fetches detailed information') and resource ('movie, TV show, or person'), and distinguishes from siblings by specifying it's for targeted content analysis by ID rather than discovery/search functions. It explicitly names the purpose as obtaining in-depth metadata for analysis.

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?

The description provides clear context about when to use this tool ('for targeted content analysis by AI agents') and implies it's for specific items identified by type and ID rather than discovery. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the many sibling tools.

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