Skip to main content
Glama
uzaysozen

imdb-mcp-server

get_top_rated_indian_movies

Retrieve top-rated Indian movies from IMDb using pagination. Specify a starting index to get 5 movies at a time from the top 250 list.

Instructions

Top 250 rated Indian movies on IMDb with pagination. Args: start: The starting index (0-based) to retrieve movies from. Returns: JSON object containing 5 top rated Indian movies starting from the specified index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the core logic for fetching and paginating top-rated Indian movies from the IMDb API.
    @mcp.tool()
    async def get_top_rated_indian_movies(start: int, ctx: Context) -> str:
        """Top 250 rated Indian movies on IMDb with pagination.
        Args:
            start: The starting index (0-based) to retrieve movies from.
        Returns:
            JSON object containing 5 top rated Indian movies starting from the specified index.
        """
        top_rated_indian_movies_url = f"{BASE_URL}/india/top-rated-indian-movies"
        top_rated_indian_movies_data = await make_imdb_request(top_rated_indian_movies_url, {}, ctx)
        if not top_rated_indian_movies_data:
            return "Unable to fetch top rated Indian movies data."
        return json.dumps(paginated_response(top_rated_indian_movies_data, start, len(top_rated_indian_movies_data)), indent=4)
  • Helper function used by the tool to make HTTP requests to the IMDb API endpoint, handling caching, API keys, and errors.
    async def make_imdb_request(url: str, querystring: dict[str, Any], ctx: Optional[Context] = None) -> Optional[Dict[str, Any]]:
        """Make a request to the IMDb API with proper error handling and caching."""
        
        # Check if it's time to clean the cache
        cache_manager.cleanup_if_needed()
        
        # Create a cache key from the URL and querystring
        cache_key = f"{url}_{str(querystring)}"
        
        # Try to get from cache first
        cached_data = cache_manager.cache.get(cache_key)
        if cached_data:
            return cached_data
        
        # Get API key from session config or fallback to environment variable
        api_key = None
        if ctx and hasattr(ctx, 'session_config') and ctx.session_config:
            api_key = ctx.session_config.rapidApiKeyImdb
        
        if not api_key:
            api_key = os.getenv("RAPID_API_KEY_IMDB")
        
        # Not in cache, make the request
        headers = {
            "x-rapidapi-key": api_key,
            "x-rapidapi-host": "imdb236.p.rapidapi.com",
        }
        
        if not api_key:
            raise ValueError("API key not found. Please set the RAPID_API_KEY_IMDB environment variable or provide rapidApiKeyImdb in the request.")
        
        try:
            response = requests.get(url, headers=headers, params=querystring, timeout=30.0)
            response.raise_for_status()
            data = response.json()
            
            # Cache the response
            cache_manager.cache.set(cache_key, data)
                
            return data
        except Exception as e:
            raise ValueError(f"Unable to fetch data from IMDb. Please try again later. Error: {e}")
  • Helper function used by the tool to format the API response into a paginated JSON structure with 5 items per page.
    def paginated_response(items, start, total_count=None):
        """Format a paginated response with a fixed page size of 5."""
        if total_count is None:
            total_count = len(items)
        
        # Validate starting index
        start = max(0, min(total_count - 1 if total_count > 0 else 0, start))
        
        # Fixed page size of 5
        page_size = 5
        end = min(start + page_size, total_count)
        
        return {
            "items": items[start:end],
            "start": start,
            "count": end - start,
            "totalCount": total_count,
            "hasMore": end < total_count,
            "nextStart": end if end < total_count else None
        }
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it specifies the dataset size (top 250), pagination behavior (5 movies per page, 0-based indexing), and return format (JSON object). It doesn't mention rate limits, authentication needs, or data freshness, but provides substantial operational context beyond basic functionality.

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 focused sentences: purpose statement, parameter explanation, and return specification. It's front-loaded with the core functionality. The 'Args:' and 'Returns:' formatting is helpful, though slightly less polished than pure prose. Every sentence earns its place by adding distinct value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 (pagination, curated list), no annotations, and the presence of an output schema (which handles return value documentation), the description is complete enough. It covers purpose, usage context, parameter semantics, and behavioral details like pagination mechanics. The output schema existence means the description doesn't need to detail return structure.

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

Parameters5/5

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

With 0% schema description coverage (the schema only shows 'start' is an integer), the description fully compensates by explaining that 'start' is 'the starting index (0-based) to retrieve movies from' and clarifies that it returns '5 top rated Indian movies starting from the specified index.' This adds crucial semantic meaning about how the parameter affects the output.

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 specific action ('retrieve movies'), resource ('top 250 rated Indian movies on IMDb'), and scope ('with pagination'). It explicitly distinguishes this tool from siblings like 'get_top_250_movies' (general top movies) and 'get_top_rated_tamil_movies' (specific language subset) by specifying the Indian focus and pagination mechanism.

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 about when to use this tool (to retrieve paginated top-rated Indian movies) and implicitly distinguishes it from alternatives like 'get_most_popular_movies' or 'search_imdb' by focusing on a specific curated list. However, it doesn't explicitly state when NOT to use it or provide direct comparison with all sibling tools.

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