Skip to main content
Glama

delete_entities

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

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

  • Handler function for delete_entities tool, including @server.tool decorator for registration. Validates input with DeleteEntitiesArgs, ensures at least one entity ID is provided, constructs payload, and delegates 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 defining the input schema (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.")
  • @server.tool decorator registers the delete_entities function as an MCP tool with its description.
    @server.tool(
        description="Remove a user/agent/app/run record entirely (and cascade-delete its memories)."
    )
Behavior4/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 effectively discloses key behavioral traits: the tool performs a destructive operation ('Remove entirely'), specifies what gets deleted (entities and their memories via cascade), and identifies the types of entities affected. However, it lacks details on permissions, rate limits, or error conditions.

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 scope. Every word earns its place by specifying the verb, resources, and cascade effect without redundancy or unnecessary elaboration.

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 destructive nature, no annotations, and an output schema (which handles return values), the description is reasonably complete. It covers the purpose, scope, and cascade behavior, though it could benefit from more explicit warnings about irreversibility or usage guidelines relative to siblings.

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 documented in the schema. The description adds value by clarifying that parameters are mutually exclusive (implied by 'a user/agent/app/run record' singular) and that deletion cascades to memories, but does not provide additional syntax or format details beyond the schema.

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 ('Remove entirely') and identifies the target resources ('user/agent/app/run record'), distinguishing it from sibling tools like delete_memory or delete_all_memories. It also specifies the cascade effect on memories, which adds important context about the scope of deletion.

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 removal of entities with memory cascading, but does not explicitly state when to use this versus alternatives like delete_memory (for individual memories) or delete_all_memories (for all memories without entity deletion). No exclusions or prerequisites are mentioned.

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/parthshr370/mem0_mcp_private'

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