Delete memories (soft-delete)
amber_delete_memorySoft-delete one or more memories to the trash so they can be restored later. Use it to remove specific memories by ID, not for account-level cleanup.
Instructions
Soft-delete one or more memories to the trash. Reversible via amber_restore_memory. Do NOT use this for account-level cleanup -- use amber_delete_account instead.
Provide memory_id (single) or memory_ids (batch, max 100). At least one is required. Idempotent: already-deleted memories are skipped. EVERY ID you send is accounted for: deleted_count plus already_deleted_ids (existed, already trashed) plus not_found_ids (no such row). ALWAYS check deleted_count against how many IDs you sent -- a batch is NOT all-or-nothing, and a shortfall usually means those memories are still being written (amber_store_memory is async), so check amber_get_store_task_status and retry rather than assuming they are gone. If the IDs are already in the trash you get deleted_count: 0 with an explanatory message (a no-op, NOT an error); code: not_found is returned only when no memory exists with those IDs -- so a no-op is distinguishable from wrong IDs. VERIFY WHAT YOU DELETED: the reply carries deleted -- the full content of every memory this call actually trashed. READ IT and confirm it is what the user meant, because an id proves nothing: if you deleted the wrong memory this is the moment to notice, and amber_restore_memory puts it straight back. Tell the user what was deleted rather than only how many. Requires an active subscription. Not rate-limited.
Errors: invalid_params (no id supplied, or both singular and plural given). A wrong TYPE -- a number where a string belongs -- is caught a layer earlier and answers invalid_input. Deleting an id that does not exist is NOT an error: deleted reports what was actually trashed, so compare its length against how many ids you sent.
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": "amber_delete_memory"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| memory_id | No | UUID of a single memory to trash. Omit if using `memory_ids` for batch. | |
| memory_ids | No | Array of memory UUIDs to trash in one call (max 100). Omit if using `memory_id` for single. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | Always `deleted`. The memories moved to the TRASH and stay restorable for 30 days; nothing is destroyed by this call. | |
| deleted | Yes | The memories this call actually trashed, in full. CHECK THESE: a count cannot tell you whether the right memory went, and this is the last moment the content is easy to see. Empty when nothing was deleted -- never absent, so there is one shape to handle. | |
| deleted_count | Yes | How many memories this call actually moved to the trash. Compare against the number of IDs you sent: any shortfall is itemised in already_deleted_ids / not_found_ids. | |
| not_found_ids | No | IDs that matched NO memory. Present only when some did not resolve. Most often these are from a store that has not finished writing yet (amber_store_memory is async) rather than wrong IDs -- check amber_get_store_task_status and retry. | |
| already_deleted_ids | No | IDs that exist but were ALREADY in the trash, so this call was a no-op for them. Present only when some were. |