Skip to main content
Glama
redis

Redis MCP Server

Official
by redis

lrange

Retrieve elements from a Redis list within a specified range. Returns a JSON string of list items or an error.

Instructions

Get elements from a Redis list within a specific range.

Returns: str: A JSON string containing the list of elements or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
startYes
stopYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main implementation of the 'lrange' tool. Uses @mcp.tool() decorator for MCP registration. Gets a Redis connection, calls r.lrange() with name/start/stop, returns JSON-encoded list or an error message.
    async def lrange(name: str, start: int, stop: int) -> Union[str, List[str]]:
        """Get elements from a Redis list within a specific range.
    
        Returns:
        str: A JSON string containing the list of elements or an error message.
        """
        try:
            r = RedisConnectionManager.get_connection()
            values = r.lrange(name, start, stop)
            if not values:
                return f"List '{name}' is empty or does not exist."
            else:
                return json.dumps(values)
        except RedisError as e:
            return f"Error retrieving values from list '{name}': {str(e)}"
  • The function signature defines the input schema: name (str), start (int), stop (int). Returns Union[str, List[str]] (JSON string on success, error string on failure).
    async def lrange(name: str, start: int, stop: int) -> Union[str, List[str]]:
  • The @mcp.tool() decorator registers 'lrange' as an MCP tool with the MCP server.
    @mcp.tool()
    async def lrange(name: str, start: int, stop: int) -> Union[str, List[str]]:
  • Imports used by lrange: RedisConnectionManager for getting Redis connections, and mcp for the @mcp.tool() decorator.
    from src.common.connection import RedisConnectionManager
    from src.common.server import mcp
    
    
    @mcp.tool()
    async def lpush(name: str, value: FieldT, expire: Optional[int] = None) -> str:
        """Push a value onto the left of a Redis list and optionally set an expiration time."""
        try:
            r = RedisConnectionManager.get_connection()
            r.lpush(name, value)
            if expire:
                r.expire(name, expire)
            return f"Value '{value}' pushed to the left of list '{name}'."
        except RedisError as e:
            return f"Error pushing value to list '{name}': {str(e)}"
    
    
    @mcp.tool()
    async def rpush(name: str, value: FieldT, expire: Optional[int] = None) -> str:
        """Push a value onto the right of a Redis list and optionally set an expiration time."""
        try:
            r = RedisConnectionManager.get_connection()
            r.rpush(name, value)
            if expire:
                r.expire(name, expire)
            return f"Value '{value}' pushed to the right of list '{name}'."
        except RedisError as e:
            return f"Error pushing value to list '{name}': {str(e)}"
    
    
    @mcp.tool()
    async def lpop(name: str) -> str:
        """Remove and return the first element from a Redis list."""
        try:
            r = RedisConnectionManager.get_connection()
            value = r.lpop(name)
            return value if value else f"List '{name}' is empty or does not exist."
        except RedisError as e:
            return f"Error popping value from list '{name}': {str(e)}"
    
    
    @mcp.tool()
    async def rpop(name: str) -> str:
        """Remove and return the last element from a Redis list."""
        try:
            r = RedisConnectionManager.get_connection()
            value = r.rpop(name)
            return value if value else f"List '{name}' is empty or does not exist."
        except RedisError as e:
            return f"Error popping value from list '{name}': {str(e)}"
    
    
    @mcp.tool()
    async def lrange(name: str, start: int, stop: int) -> Union[str, List[str]]:
        """Get elements from a Redis list within a specific range.
    
        Returns:
        str: A JSON string containing the list of elements or an error message.
        """
        try:
            r = RedisConnectionManager.get_connection()
            values = r.lrange(name, start, stop)
            if not values:
                return f"List '{name}' is empty or does not exist."
            else:
                return json.dumps(values)
        except RedisError as e:
            return f"Error retrieving values from list '{name}': {str(e)}"
    
    
    @mcp.tool()
    async def llen(name: str) -> int:
        """Get the length of a Redis list."""
        try:
            r = RedisConnectionManager.get_connection()
            return r.llen(name)
        except RedisError as e:
            return f"Error retrieving length of list '{name}': {str(e)}"
    
    
    @mcp.tool()
    async def lrem(name: str, count: int, element: FieldT) -> str:
        """Remove elements from a Redis list.
    
        Args:
            name: The name of the list
            count: Number of elements to remove (0 = all, positive = from head, negative = from tail)
            element: The element value to remove
    
        Returns:
            A string indicating the number of elements removed.
        """
        try:
            r = RedisConnectionManager.get_connection()
            removed_count = r.lrem(name, count, element)
    
            if removed_count == 0:
                return f"Element '{element}' not found in list '{name}' or list does not exist."
            else:
                return f"Removed {removed_count} occurrence(s) of '{element}' from list '{name}'."
    
        except RedisError as e:
            return f"Error removing element from list '{name}': {str(e)}"
Behavior2/5

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

Without annotations, the description only mentions return type (string) but does not disclose side effects (none), error conditions, bounds behavior, or result format details. Minimal 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.

Conciseness3/5

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

Very concise (two sentences) but lacks necessary detail. It is efficient but at the cost of clarity.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of many sibling list tools, no output schema details, and no annotations, the description is incomplete. It fails to clarify Redis index conventions, error handling, or return format specifics.

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

Parameters1/5

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

Schema has 3 parameters (name, start, stop) with 0% description coverage. The description does not explain the meaning of start/stop (e.g., inclusive/exclusive, indexing convention), leaving them ambiguous.

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 action ('Get elements'), resource ('Redis list'), and operation ('within a specific range'). It distinguishes from sibling tools like llen, lpop, lpush, etc.

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 on when to use this tool versus other list operations (e.g., lrange vs. llen or lindex). No context about prerequisites or use cases.

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/redis/mcp-redis'

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