Skip to main content
Glama
uzaysozen

imdb-mcp-server

get_types

Retrieve all available media types from IMDb data to filter and categorize movies, TV shows, and upcoming releases.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function that implements the get_types tool logic. It makes an API request to fetch available types and returns a JSON string.
    @mcp.tool()
    async def get_types(ctx: Context) -> str:
        """Get all types.
        Returns:
            JSON object containing all types.
        """
        types_url = f"{BASE_URL}/types"
        types_data = await make_imdb_request(types_url, {}, ctx)
        if not types_data:
            return "Unable to fetch types data."
        return json.dumps(types_data, indent=4)
  • Registration of all tools, including get_types, via register_tools call in the smithery HTTP server creation.
    register_tools(server)
  • Registration of all tools, including get_types, via register_tools call in stdio mode.
    register_tools(server)
  • Docstring reference to get_types tool in the search_imdb tool description.
    type: The type of the movie to search for. Get all possible types with get_types().
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 the tool returns 'JSON object containing all types' which provides basic output information, but doesn't disclose important behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, or what happens if no types exist. The description is minimal and lacks behavioral context.

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 extremely concise with just two brief sentences. The first sentence states the action, and the second describes the return format. There's no wasted verbiage, though some might argue it's too minimal given the lack of context about what 'types' means in this domain.

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 (which handles return value documentation) and zero parameters with 100% schema coverage, the description provides the minimum viable information. However, for a tool with no annotations and many similar siblings, the description should do more to clarify what 'types' refers to in this specific context to help the agent distinguish it from other get_* tools.

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, and schema description coverage is 100%. With no parameters to document, the description doesn't need to add parameter semantics. The baseline for zero parameters with high schema coverage is 4, as there's nothing missing to compensate for.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the purpose as 'Get all types' which is a clear verb+resource combination. However, it doesn't distinguish this tool from its many siblings (like get_genres, get_languages, get_directors) that also retrieve specific data categories. The description doesn't clarify what 'types' refers to in this context.

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?

No guidance is provided about when to use this tool versus alternatives. With 22 sibling tools on the server, the description offers no context about what 'types' are or when this retrieval would be appropriate compared to other get_* tools. The description simply states what it does without usage context.

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