Skip to main content
Glama
arjunkmrm

Mem0 MCP Server

delete_entities

Remove user, agent, app, or run records and their associated memories from the Mem0 memory system to manage stored data.

Instructions

Remove a user/agent/app/run record entirely (and cascade-delete its memories).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNoDelete this user and its memories.
agent_idNoDelete this agent and its memories.
app_idNoDelete this app and its memories.
run_idNoDelete this run and its memories.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Full handler function for the 'delete_entities' tool, including registration decorator (@server.tool), input validation with DeleteEntitiesArgs, scope validation, and call to Mem0 client's delete_users method.
    @server.tool(
        description="Remove a user/agent/app/run record entirely (and cascade-delete its memories)."
    )
    def delete_entities(
        user_id: Annotated[
            Optional[str], Field(default=None, description="Delete this user and its memories.")
        ] = None,
        agent_id: Annotated[
            Optional[str], Field(default=None, description="Delete this agent and its memories.")
        ] = None,
        app_id: Annotated[
            Optional[str], Field(default=None, description="Delete this app and its memories.")
        ] = None,
        run_id: Annotated[
            Optional[str], Field(default=None, description="Delete this run and its memories.")
        ] = None,
        ctx: Context | None = None,
    ) -> str:
        """Delete a user/agent/app/run (and its memories) once the user confirms the scope."""
    
        api_key, _, _ = _resolve_settings(ctx)
        args = DeleteEntitiesArgs(
            user_id=user_id,
            agent_id=agent_id,
            app_id=app_id,
            run_id=run_id,
        )
        if not any([args.user_id, args.agent_id, args.app_id, args.run_id]):
            return json.dumps(
                {
                    "error": "scope_missing",
                    "detail": "Provide user_id, agent_id, app_id, or run_id before calling delete_entities.",
                },
                ensure_ascii=False,
            )
        payload = args.model_dump(exclude_none=True)
        client = _mem0_client(api_key)
        return _mem0_call(client.delete_users, **payload)
  • Pydantic BaseModel schema defining the input arguments for the delete_entities tool.
    class DeleteEntitiesArgs(BaseModel):
        user_id: Optional[str] = Field(None, description="Delete this user and all related memories.")
        agent_id: Optional[str] = Field(None, description="Delete this agent and its memories.")
        app_id: Optional[str] = Field(None, description="Delete this app and its memories.")
        run_id: Optional[str] = Field(None, description="Delete this run and its memories.")
  • MCP server tool registration for 'delete_entities' using FastMCP @server.tool decorator.
    @server.tool(
        description="Remove a user/agent/app/run record entirely (and cascade-delete its memories)."
    )
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. It discloses the destructive nature ('Remove entirely') and cascade behavior, which is essential. However, it lacks details on permissions required, whether deletion is reversible, rate limits, error conditions, or what the output contains. For a high-risk deletion tool, this is insufficient.

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?

The description is a single, efficient sentence that front-loads the core action and key behavioral detail (cascade-delete). Every word earns its place with zero waste or redundancy.

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 high-risk nature of this tool (permanent deletion with cascading effects), no annotations, and an output schema (which may cover return values), the description is minimally adequate. It covers the what and cascade effect but misses critical context like permissions, irreversibility, and error handling that an agent needs for safe invocation.

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 description coverage is 100%, with each parameter clearly documented in the schema itself. The description adds no additional parameter semantics beyond implying that exactly one of the four IDs should be provided (though not explicitly stated). Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Remove') and specifies the resources ('user/agent/app/run record entirely'), distinguishing it from sibling tools like delete_memory or delete_all_memories. It adds the critical detail of cascade-deleting memories, which is not obvious from the tool name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for permanent deletion of entities with their memories, but does not explicitly state when to use this versus alternatives like delete_memory (for individual memories) or delete_all_memories (for bulk memory deletion without entity removal). No guidance on prerequisites, permissions, or recovery options is provided.

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/arjunkmrm/mem0-mcp'

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