Skip to main content
Glama
uzaysozen

imdb-mcp-server

get_genres

Retrieve a complete list of all available movie and TV show genres from IMDb's comprehensive database for content categorization and filtering.

Instructions

Get all genres. Returns: JSON object containing all genres.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_genres' MCP tool. It makes an API request to fetch all genres from IMDb and returns them as a JSON string.
    @mcp.tool()
    async def get_genres(ctx: Context) -> str:
        """Get all genres.
        Returns:
            JSON object containing all genres.
        """
        genres_url = f"{BASE_URL}/genres"
        genres_data = await make_imdb_request(genres_url, {}, ctx)
        if not genres_data:
            return "Unable to fetch genres data."
        return json.dumps(genres_data, indent=4)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Returns: JSON object containing all genres', which adds some behavioral context about the output format. However, it lacks critical details like whether this is a read-only operation, potential rate limits, authentication needs, or error conditions. For a tool with zero annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief with two sentences, but the structure is slightly awkward with 'Returns:' on a separate line. It's front-loaded with the main purpose, but the second sentence could be integrated more smoothly. It avoids unnecessary verbosity.

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 the tool has an output schema (context signals indicate 'Has output schema: true'), the description doesn't need to detail return values. However, with no annotations and simple functionality, the description is minimally adequate. It could benefit from more behavioral context or usage guidance to be fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters, and it correctly doesn't mention any. This is appropriate for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 'Get all genres', which is a specific verb+resource combination. It distinguishes itself from siblings by focusing on genres rather than other data types like movies, directors, or languages. However, it doesn't explicitly differentiate from potential similar tools (none exist in siblings).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or comparisons with sibling tools like get_types or other data retrieval tools. The agent must infer usage based solely on the tool name and description.

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/uzaysozen/imdb-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server