Skip to main content
Glama
drakonkat

wizzy-mcp-tmdb

search_keywords

Find TMDB keywords to categorize content and optimize search results for movies and TV shows using text queries.

Instructions

Searches for TMDB keywords (tags) by text query. Input: query (required search string), page (optional page number). Output: JSON with paginated keyword results. Purpose: Discover keywords for content categorization and search optimization by AI agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
queryYesSearch query for keywords

Implementation Reference

  • The handler function for the search_keywords tool. It calls tmdbFetch with '/search/keyword' endpoint using query and optional page parameters, then returns the JSON-stringified data wrapped in MCP content format.
    handler: async ({query, page}) => {
        const data = await tmdbFetch('/search/keyword', {query, page});
        return {content: [{type: 'text', text: JSON.stringify(data, null, 2)}]};
    }
  • The inputSchema for search_keywords tool, specifying required 'query' string and optional 'page' number (min 1).
    inputSchema: {
        type: "object",
        properties: {query: {type: "string", description: "Search query for keywords"}, page: {type: "number", minimum: 1, description: "Page number"}},
        required: ["query"],
        additionalProperties: false
    },
  • The complete tool registration object for 'search_keywords' within the tools array, which is used by MCP server handlers for listing and calling tools.
    {
        name: "search_keywords",
        description: "Searches for TMDB keywords (tags) by text query. Input: query (required search string), page (optional page number). Output: JSON with paginated keyword results. Purpose: Discover keywords for content categorization and search optimization by AI agents.",
        inputSchema: {
            type: "object",
            properties: {query: {type: "string", description: "Search query for keywords"}, page: {type: "number", minimum: 1, description: "Page number"}},
            required: ["query"],
            additionalProperties: false
        },
        handler: async ({query, page}) => {
            const data = await tmdbFetch('/search/keyword', {query, page});
            return {content: [{type: 'text', text: JSON.stringify(data, null, 2)}]};
        }
    },
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. It mentions the output format ('JSON with paginated keyword results') and purpose, but lacks details on behavioral traits such as rate limits, authentication needs, error handling, or what 'paginated' entails (e.g., page size). This is a significant gap for a search tool with no annotation coverage.

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 with three sentences that cover action, input, output, and purpose. It is front-loaded with the core functionality, though the last sentence could be more tightly integrated. There is no wasted text, but minor improvements in flow are possible.

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 context but is incomplete. It covers the purpose and output format at a high level, but lacks details on behavioral aspects and does not fully compensate for the missing structured data, leaving gaps for effective tool invocation.

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 both parameters ('query' and 'page'). The description adds minimal value by restating the input and output in general terms, but does not provide additional semantics beyond what the schema offers, such as query formatting examples or page behavior details.

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 ('Searches for') and resource ('TMDB keywords (tags)'), specifies the domain ('by text query'), and distinguishes from siblings by focusing on keywords rather than movies, TV shows, or people. It also mentions the purpose for AI agents, which adds context.

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 for 'content categorization and search optimization by AI agents,' which provides some context, but it does not explicitly state when to use this tool versus alternatives like 'search_tmdb' or other keyword-related tools. No exclusions or clear alternatives are mentioned.

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