Restore deleted memories
amber_restore_memoryRestore deleted memories from the trash to make them searchable and visible again. Use after searching or listing deleted memories to recover accidentally removed content.
Instructions
Un-delete memories from the trash, making them searchable and visible in amber_list_memories again. Use after amber_search_deleted_memories or amber_list_deleted_memories to recover accidentally deleted content. Do NOT use for new content -- use amber_store_memory instead.
Provide memory_id (single) or memory_ids (batch, max 100). At least one is required. Idempotent: already-active memories are skipped. Side effects: moves memories from trash to active. VERIFY WHAT CAME BACK: the reply carries restored -- the full content of every memory this call actually un-trashed. READ IT and confirm it is the one the user meant, because an id proves nothing. EVERY ID you send is accounted for: restored_count plus already_active_ids plus not_found_ids. ALWAYS check restored_count against how many IDs you sent -- a batch is NOT all-or-nothing. If the IDs are already active you get restored_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. Requires an active subscription. Not rate-limited.
Errors: invalid_params (no id supplied, or both singular and plural given); a wrong TYPE answers invalid_input from the schema layer. Restoring something that was never deleted is not an error either; it comes back in already_active_ids.
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_restore_memory"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| memory_id | No | UUID of a single memory to restore. Omit if using `memory_ids` for batch. | |
| memory_ids | No | Array of memory UUIDs to restore in one call (max 100). Omit if using `memory_id` for single. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | Always `restored`, including when nothing changed because every id was already active. | |
| restored | Yes | The memories this call actually brought back, in full. CHECK THESE: a count cannot tell you which memory was recovered, and that is the whole question after a wrong delete. Empty when nothing was restored -- never absent, so there is one shape to handle. | |
| 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. | |
| restored_count | Yes | How many memories this call actually restored. Compare against the number of IDs you sent: any shortfall is itemised in already_active_ids / not_found_ids. | |
| already_active_ids | No | IDs that exist but were ALREADY active, so this call was a no-op for them. Present only when some were. |