Skip to main content
Glama
redis

Redis MCP Server

Official
by redis

lpush

Add a value to the beginning of a Redis list, with optional time-to-live expiration.

Instructions

Push a value onto the left of a Redis list and optionally set an expiration time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
valueYes
expireNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the 'lpush' MCP tool. Uses @mcp.tool() decorator to register as a tool. Gets a Redis connection, calls LPUSH to push a value to the left of a list, optionally sets an expiration, and returns a success/error message.
    @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)}"
  • Input schema for the 'lpush' tool: takes 'name' (str, the list name), 'value' (any field type), optional 'expire' (int). Returns a string.
    async def lpush(name: str, value: FieldT, expire: Optional[int] = None) -> str:
  • The FastMCP server instance. The 'lpush' function in src/tools/list.py is registered as a tool via the @mcp.tool() decorator.
    # Initialize FastMCP server
    mcp = FastMCP(
  • The load_tools() function that dynamically imports all modules from src.tools, which triggers the @mcp.tool() decorators and registers the tools including 'lpush'.
    def load_tools():
        import src.tools as tools_pkg
    
        for _, module_name, _ in pkgutil.iter_modules(tools_pkg.__path__):
            importlib.import_module(f"src.tools.{module_name}")
    
    
    # Initialize FastMCP server
    mcp = FastMCP(
        "Redis MCP Server", dependencies=["redis", "python-dotenv", "numpy", "aiohttp"]
    )
    
    # Load tools
    load_tools()
Behavior3/5

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

Discloses the core write operation and optional expiration, but does not mention return value (list length), error handling for non-list keys, or TTL unit. Without annotations, description carries full burden and is moderately transparent.

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

Conciseness5/5

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

Single sentence, 14 words, no redundancy. Front-loaded with core action and optional feature. Efficient.

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?

Tool has 3 parameters, no annotations, and output schema exists but description doesn't mention return value (list length). Lacks details like TTL units or effect on existing TTL. Adequate but incomplete for a simple tool.

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

Parameters3/5

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

Schema coverage is 0%, so description should add meaning. It explains 'value' as the data to push and 'expire' as optional TTL, but 'name' (the list key) is only implied. Partially compensates but not fully explicit for all parameters.

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?

Clearly states it pushes a value onto the left of a Redis list and optionally sets expiration, distinguishing it from rpush (right push) and other list operations. The verb 'push' and resource 'Redis list' are specific.

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 explicit guidance on when to use this tool vs alternatives like rpush, lset, or lpush with expire. Only implicit differentiation from sibling names. No when-not or alternative comparisons.

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