Skip to main content
Glama

List Memories

recall_list
Read-onlyIdempotent

Retrieve a paginated list of stored memories, optionally filtered by type, returning summaries and pagination metadata.

Instructions

List stored memories (index view, no bodies), optionally filtered by type.

Args:

  • type: optional filter to a single memory type

  • limit: max results (default 20)

  • offset: number of results to skip, for pagination (default 0)

  • response_format: 'markdown' (default) or 'json'

Returns memory summaries plus pagination metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional: restrict to a single memory type
limitNoMaximum number of results to return
offsetNoResults to skip for pagination
response_formatNo'markdown' for human-readable, 'json' for structured datamarkdown
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds context beyond annotations: returns summaries (no bodies) plus pagination metadata, and lists parameters' effect. Annotations declare readOnly=true, idempotent=true, destructive=false, consistent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One-line purpose plus bulleted parameters, no fluff, front-loaded with key info.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema but describes returns; covers all 4 parameters with defaults and options; adequate for a non-destructive listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% so baseline 3; description adds usage notes (defaults for limit/offset, response_format options) beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'List stored memories (index view, no bodies)' with verb and resource, and distinguishes from siblings like recall_get (full body) and recall_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for listing/filtering memories; could explicitly contrast with recall_get or recall_search but provides clear parameter guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andrewhomeyer/recall-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server