Skip to main content
Glama
drakonkat

wizzy-mcp-tmdb

by drakonkat
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

discover_by_provider

Find movies and TV shows available on specific streaming services in your region to help you discover content you can watch immediately.

Instructions

Discovers movies or TV shows available on specific streaming providers in a region. Input: type (optional: tv|movie, default tv), with_watch_providers (required comma-separated provider IDs), watch_region (required ISO 3166-1), language (optional ISO 639-1, default en), page (optional), sort_by (optional). Output: JSON with paginated results. Purpose: Personalized content discovery based on streaming availability for AI agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoISO 639-1 language (e.g., en)
pageNoPage number
sort_byNoSort order (e.g., release_date.desc, first_air_date.desc, popularity.desc)
typeNoMedia type to discover: tv (default) or movie
watch_regionYesISO 3166-1 region code (e.g., IS)
with_watch_providersYesProvider ID(s), comma-separated (e.g., '8'), from service get_watch_providers

Implementation Reference

  • mcp-tmdb-server.js:438-454 (handler)
    The async handler function that executes the tool logic by calling the TMDB /discover/{type} API endpoint with parameters for filtering by watch providers in a specific region.
    handler: async ({
                     type = "tv",
                     with_watch_providers,
                     watch_region,
                     language = "en",
                     page = 1,
                     sort_by = "release_date.desc"
                 }) => {
    const data = await tmdbFetch(`/discover/${type}`, {
        language,
        page,
        with_watch_providers,
        sort_by,
        watch_region
    });
    return {content: [{type: "text", text: JSON.stringify(data, null, 2)}]};
}
  • mcp-tmdb-server.js:415-437 (schema)
    The inputSchema JSON Schema object defining the expected input parameters, types, descriptions, and requirements for the tool.
    inputSchema: {
    type: "object",
    properties: {
        type: {
            type: "string",
            enum: ["tv", "movie"],
            description: "Media type to discover: tv (default) or movie"
        },
        with_watch_providers: {
            type: "string",
            description: "Provider ID(s), comma-separated (e.g., '8'), from service get_watch_providers"
        },
        watch_region: {type: "string", description: "ISO 3166-1 region code (e.g., IS)"},
        language: {type: "string", description: "ISO 639-1 language (e.g., en)"},
        page: {type: "number", minimum: 1, description: "Page number"},
        sort_by: {
            type: "string",
            description: "Sort order (e.g., release_date.desc, first_air_date.desc, popularity.desc)"
        }
    },
    required: ["with_watch_providers", "watch_region"],
    additionalProperties: false
},
  • mcp-tmdb-server.js:412-455 (registration)
    The complete tool object definition within the 'tools' array, which serves as the registration point for the MCP server to list and invoke this tool via name matching.
    {
    name: "discover_by_provider",
    description: "Discovers movies or TV shows available on specific streaming providers in a region. Input: type (optional: tv|movie, default tv), with_watch_providers (required comma-separated provider IDs), watch_region (required ISO 3166-1), language (optional ISO 639-1, default en), page (optional), sort_by (optional). Output: JSON with paginated results. Purpose: Personalized content discovery based on streaming availability for AI agents.",
    inputSchema: {
        type: "object",
        properties: {
            type: {
                type: "string",
                enum: ["tv", "movie"],
                description: "Media type to discover: tv (default) or movie"
            },
            with_watch_providers: {
                type: "string",
                description: "Provider ID(s), comma-separated (e.g., '8'), from service get_watch_providers"
            },
            watch_region: {type: "string", description: "ISO 3166-1 region code (e.g., IS)"},
            language: {type: "string", description: "ISO 639-1 language (e.g., en)"},
            page: {type: "number", minimum: 1, description: "Page number"},
            sort_by: {
                type: "string",
                description: "Sort order (e.g., release_date.desc, first_air_date.desc, popularity.desc)"
            }
        },
        required: ["with_watch_providers", "watch_region"],
        additionalProperties: false
    },
    handler: async ({
                         type = "tv",
                         with_watch_providers,
                         watch_region,
                         language = "en",
                         page = 1,
                         sort_by = "release_date.desc"
                     }) => {
        const data = await tmdbFetch(`/discover/${type}`, {
            language,
            page,
            with_watch_providers,
            sort_by,
            watch_region
        });
        return {content: [{type: "text", text: JSON.stringify(data, null, 2)}]};
    }
},

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'Output: JSON with paginated results' which is helpful, but doesn't disclose rate limits, authentication needs, error conditions, or what happens with invalid provider IDs. It describes the core behavior adequately but lacks operational details that would help an agent use it safely and effectively.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The parameter listing is somewhat redundant given the schema, but the final sentence adds useful context about the tool's purpose for AI agents. Most sentences earn their place, though the parameter enumeration could be more concise.

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 6 parameters, no annotations, and no output schema, the description provides adequate coverage for a read-only discovery tool. It explains the purpose, lists parameters, and mentions the output format. However, it lacks details about error handling, rate limits, and doesn't fully compensate for the missing output schema by describing result structure beyond 'JSON with paginated results.'

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 beyond the schema by listing parameters but doesn't provide additional semantic context like examples of provider IDs beyond referencing 'from service get_watch_providers' (which is already in the schema). 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 tool's purpose with specific verbs ('discovers movies or TV shows') and resources ('available on specific streaming providers in a region'). It distinguishes from siblings like discover_movies and discover_tv by specifying provider-based filtering and explicitly mentions 'Personalized content discovery based on streaming availability' which differentiates it from general discovery tools.

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 for when to use this tool ('Personalized content discovery based on streaming availability'), but doesn't explicitly state when NOT to use it or name specific alternatives. It implies usage for provider-filtered discovery versus general discovery tools, but lacks explicit exclusions or comparisons to siblings like get_watch_providers.

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