Tool reference · Team server (remote)
memory_delete
Soft-deletes a record after checking its revision, keeping it and its history available for audit.
team server /mcp
Caution. This is a soft delete: status becomes "deleted" and the record leaves search, but it still appears in memory_get, memory_history and memory_export. There is no undelete tool in this catalogue. Requires write access to the scope.
When to use
- A record is wrong or no longer applies and should stop showing up in search.
- You want the deletion reason and who deleted it recorded.
- You need a safe retry after a timeout, using the same request_id.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
scope | { kind, team_id } | — | — |
idrequired | integer | — | — |
request_id | string (uuid) | — | — |
expected_revisionrequired | integer | — | — |
reasonrequired | string | — | (min length 1, max length 2,000) |
Example
Arguments
{
"scope": {
"kind": "personal"
},
"id": 44,
"request_id": "9e8d7c6b-5a49-4382-a1b0-c9d8e7f6a5b4",
"expected_revision": 1,
"reason": "Outdated: fixed by upgrading pgbouncer"
}Result shape
{
"scope": {
"kind": "personal",
"team_id": null
},
"scope_tags": [
"scope:personal"
],
"data": {
"id": 44,
"content": "pgbouncer session mode broke prepared statements locally",
"status": "deleted",
"created_by": {
"user_id": "vasya",
"display_name": "Vasya",
"client": "codex"
},
"updated_by": {
"user_id": "vasya",
"display_name": "Vasya",
"client": "codex"
},
"revision": 2
}
}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:
Soft-delete an exact record with revision checking.