List deleted memories (trash)
amber_list_deleted_memoriesBrowse trashed memories in reverse deletion order with cursor pagination, then restore items or search the trash by meaning. Read-only and does not permanently delete anything.
Instructions
Browse the trash in reverse chronological order of deletion (most recently deleted first). Supports cursor pagination via after_id. has_more tells you whether another page exists. Use amber_restore_memory to bring an item back, or amber_search_deleted_memories for meaning-based search within the trash.
Each result includes full content (not truncated), metadata, topics, creation timestamp, and deletion timestamp. Pass metadata_filter for an EXHAUSTIVE exact-match filter over the trash (same as amber_list_memories). Read-only -- does not modify or permanently delete any memories. Not rate-limited. Requires an active subscription.
Returns memories array, next_cursor (null if no more pages), and has_more boolean.
Errors: invalid_input (a bad cursor, limit, or filter type).
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_list_deleted_memories"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of deleted memories per page (default 20, min 1, max 100). Use smaller values (5-10) for quick checks, larger values (50-100) for bulk review. Omit to use the default of 20. | |
| after_id | No | Pagination cursor (memory ID string). Pass the `next_cursor` value from a previous response to fetch the next page. Omit on the first call to start from the most recently deleted memory. Do not fabricate cursor values. | |
| metadata_filter | No | Optional EXACT-match metadata filter, e.g. { "qa_batch": "2026-07-21" }. Values must be SCALARS (string/number/boolean/null) -- operator objects like {"$ne": ...} and nested objects are NOT supported (rejected with invalid_input). Matching is TYPE-STRICT as well as exact: metadata stored as the number 5 is matched by 5, NOT by "5". A null VALUE matches only memories that explicitly stored a null under that key -- a memory missing the key entirely does NOT match, exactly as a wrong value would not. If a value reached you stringified (from JSON, a config file, a spreadsheet export), convert it back first -- a type mismatch returns an empty result set that looks exactly like "no such data". Filters at the database level and returns EVERY matching trashed memory across pages (same exhaustive semantics as amber_list_memories). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| has_more | Yes | Whether another page exists. Prefer this over guessing from the page size. | |
| memories | Yes | This page of memories currently in the trash, newest first. Restore one with `amber_restore_memory`. | |
| next_cursor | Yes | Pass this back as `after_id` for the next page (the parameter is `after_id`; this said `cursor` until 2026-09-19, which is not a parameter this tool has). Null on the last page. Opaque: do not build or edit one. |