List memories
list_memoriesBrowse recent memories in reverse-chronological order to audit saved items or collect specific memory IDs. Supports filtering by type, tags, workspace, and group.
Instructions
List recent memories in reverse-chronological order (read-only). When to use: audit what is saved, browse a collection, or collect memory IDs for get_memory or forget. When NOT: semantic search by topic → recall; one full record → get_memory; aggregate counts only → memory_stats. Behavior: default 20 results (plan-capped), ordered by created_at descending; empty set returns a message suggesting remember; full_content controls preview in the message text (120 chars); structured memories[] always includes full content. To list a team workspace instead of personal memory, pass workspace: .
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Optional tags. A tag like project:my-app also sets collection automatically. | |
| type | No | Memory category: general, preference, fact, instruction, or conversation. Omit to include all types. | |
| limit | No | Positive integer max results. Omit for server default (20). Capped per your plan. | |
| group_id | No | UUID of a shared group. Required with visibility=shared when group_name is not set. | |
| workspace | No | To operate on a team workspace, pass its exact name, slug, or ID (e.g. "Acme"). Omit — or pass "personal" — for your personal memory (default). Every response echoes resolved_workspace so you can confirm where the operation actually happened. If the user mentions a project or team name in their message, check the memory://workspaces resource (or call list_collections) for the exact matching name BEFORE calling this tool, and pass it as workspace — do not ask the user to spell it out if it already matches one of their workspaces. | |
| collection | No | Scope slug (e.g. project:memxus, personal:preferences). GitHub/Notion connector syncs use project:<slug> — one collection per project. Partial names work; call list_collections when unsure. | |
| group_name | No | Exact group name (case-insensitive). Alternative to group_id for shared memories. | |
| visibility | No | Optional. Defaults to user dashboard preference (private unless include_group_memories_in_context is on). | |
| full_content | No | When true, message text shows full memory content. When false, message previews truncate at 120 chars; memories[].content in structured output is always full. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Memories returned (0–limit). Zero triggers empty-state message. | |
| message | Yes | Human-readable listing; previews truncate at 120 chars unless full_content=true. | |
| memories | Yes | Newest-first matches. Each item includes full content in structured output. | |
| resolved_workspace | No | The workspace this call actually operated on (defense against writing to the wrong team by typo or name collision). id=null means Personal. |