Tool reference · Edit, history & reports
memory_delete
Removes one record from search results by marking it deleted and dropping its embeddings. With hard: true it erases the record for good, with its earlier versions and every derived copy.
local stdio server writes destructive idempotent
Caution. Without hard, the row stays in the database with status deleted and there is no tool to bring it back into search. hard: true cannot be undone: it also removes earlier versions, Chroma copies and the text in raw call logs, and works on personal (SQLite) memory only. Use memory_update instead if the record only needs correcting.
When to use
- A saved record is wrong and should never be returned again.
- You saved something by mistake, such as a duplicate or a note meant for another project.
- A record holds personal data or anything that must not be kept: use hard: true.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
idrequired | integer | — | Knowledge record ID to delete |
hard | boolean | false | Erase permanently instead of hiding; cannot be undone |
Example
Arguments
{
"id": 1843
}Result shape
{
"deleted": true,
"id": 1843,
"content_preview": "Staging database runs on port 5433; production uses 5432."
}Values are illustrative; the keys follow the server's handler. MCP clients receive the result as JSON text content.
Server description
The description the server sends to your agent in tools/list, captured from the v14.7.0 source:
Delete a knowledge record. By default a soft delete: the record leaves search results and vectors but stays in the database. hard=true erases it for good, with its earlier versions, derived rows and its text in the raw call log (use for personal data or anything that must not be kept).