Skip to main content
Glama

Delete memories

memory_forget
DestructiveIdempotent

Delete stored memories by provider: supply memory_id for mem0, or omit it to drop a Hindsight bank. Confirm before deleting; unavailable on Cognee.

Instructions

Delete memories: mem0 needs memory_id; on Hindsight a bank without memory_id drops the whole bank. Confirm with the user first. Not available on Cognee.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNoHindsight bank to drop (when memory_id omitted), or mem0 user_id scope
memory_idNoProvider memory id (required for mem0 deletes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.0
    • changedInput schema / properties / bank / description
      Previous value: -"Hindsight bank to delete, or mem0 user_id scope for bulk delete"New value: +"Hindsight bank to drop (when memory_id omitted), or mem0 user_id scope"
    • changedInput schema / properties / memory_id / description
      Previous value: -"Provider memory id (mem0)"New value: +"Provider memory id (required for mem0 deletes)"
  2. First observedv0.6.3

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the safety profile is known; the description adds the crucial blast-radius detail that omitting memory_id on Hindsight drops an entire bank, plus a required confirmation step. It stops short of stating irreversibility or what the deletion response looks like.

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?

Three compact sentences, front-loaded with the action and provider split, then the destructive edge case, then the safety instruction. No filler.

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?

For a two-parameter destructive tool with no output schema, the agent has provider scope, the catastrophic parameter combination, and the confirmation requirement. Only the post-deletion return behavior is unaddressed, which is a minor gap.

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

Parameters4/5

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

Schema coverage is 100% and the property descriptions already explain bank and memory_id per provider, so a baseline 3 applies. The description adds the cross-parameter dependency (mem0 deletes need memory_id) and the danger of the omitted-parameter case, which is genuine semantic value 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?

States a specific verb and resource ('Delete memories') and immediately differentiates behavior per provider: mem0 keys on memory_id while Hindsight drops a whole bank. That is enough for an agent to distinguish it from siblings like memory_consolidate or memory_add without opening a schema.

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

Usage Guidelines5/5

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

Explicit prerequisites and exclusions: mem0 requires memory_id, Hindsight without memory_id drops the entire bank, and the tool is unavailable on Cognee. It also mandates user confirmation before invoking, which is a usage rule, not just a description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.