Skip to main content
Glama
uzaysozen

imdb-mcp-server

get_upcoming_releases

Retrieve upcoming movie and TV releases from IMDb for specific countries with paginated results.

Instructions

Get the upcoming releases from IMDb with pagination. Args: country_code: The country code to get the upcoming releases for. type: The type of the upcoming releases to get. Possible values: "TV", "MOVIE". start: The starting index (0-based) to retrieve releases from. Returns: JSON object containing 5 upcoming releases starting from the specified index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeYes
typeYes
startYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_upcoming_releases' tool. It is decorated with @mcp.tool() for automatic registration. Fetches upcoming releases data from the IMDb API using the provided country_code and type parameters, handles pagination with the start index using the paginated_response helper, and returns a JSON string of the results or an error message if data is unavailable.
    @mcp.tool()
    async def get_upcoming_releases(country_code: str, type: str, start: int, ctx: Context) -> str:
        """Get the upcoming releases from IMDb with pagination.
        Args:
            country_code: The country code to get the upcoming releases for.
            type: The type of the upcoming releases to get. Possible values: "TV", "MOVIE".
            start: The starting index (0-based) to retrieve releases from.
        Returns:
            JSON object containing 5 upcoming releases starting from the specified index.
        """
        upcoming_releases_url = f"{BASE_URL}/upcoming-releases"
        upcoming_releases_data = await make_imdb_request(upcoming_releases_url, {"countryCode": country_code, "type": type}, ctx)
        if not upcoming_releases_data:
            return "Unable to fetch upcoming releases data."
        return json.dumps(paginated_response(upcoming_releases_data, start, len(upcoming_releases_data)), indent=4)
Behavior2/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 mentions 'pagination' and specifies that it returns '5 upcoming releases starting from the specified index,' which adds useful context about output format and limitations. However, it doesn't cover error handling, rate limits, authentication needs, or whether the data is static or real-time, leaving significant gaps for a 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 well-structured and appropriately sized. It front-loads the core purpose in the first sentence, followed by a clear breakdown of arguments and returns. Each sentence adds value, with no redundant information, though it could be slightly more concise by integrating the returns into the initial statement.

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?

Given the tool's moderate complexity (3 required parameters) and the presence of an output schema, the description is fairly complete. It covers parameter semantics adequately and specifies the return format (JSON with 5 items), reducing the need to explain outputs. However, without annotations, it lacks details on behavioral aspects like error cases or performance, leaving room for improvement.

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 description adds substantial meaning beyond the input schema, which has 0% description coverage. It explains each parameter's purpose: 'country_code' for country filtering, 'type' with possible values 'TV' or 'MOVIE', and 'start' as a 0-based index. This compensates well for the schema's lack of descriptions, though it doesn't detail format constraints (e.g., country code standards).

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: 'Get the upcoming releases from IMDb with pagination.' It specifies the resource (upcoming releases from IMDb) and the action (get), but doesn't explicitly differentiate from sibling tools like 'get_upcoming_indian_movies' or 'get_most_popular_movies' beyond the 'upcoming' qualifier.

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 on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'get_upcoming_indian_movies' (which might be a subset) or 'search_imdb' (which might offer broader filtering), nor does it specify prerequisites or exclusions for usage.

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