Skip to main content
Glama

memory_list

List memories using filters for text, metadata, tags, and dates. Sort by importance or choose between preview and full content.

Instructions

List memories, optionally filtering by substring query or metadata.

Returns compact previews by default to reduce context usage. Use content_mode="full" when you need the complete content. Use memory_get to fetch full content for specific IDs.

Args: query: Optional text search query metadata_filters: Optional metadata filters limit: Maximum results (default: 20). Pass -1 for unlimited. offset: Number of filtered results to skip (default: 0) date_from: Optional date filter (ISO format or relative like "7d", "1m", "1y") date_to: Optional date filter (ISO format or relative like "7d", "1m", "1y") tags_any: Match memories with ANY of these tags (OR logic) tags_all: Match memories with ALL of these tags (AND logic) tags_none: Exclude memories with ANY of these tags (NOT logic) sort_by_importance: Sort results by importance score (default: False, sorts by date) content_mode: "preview" (default) returns truncated content_preview; "full" returns complete content preview_chars: Max chars for preview (default: 120, ignored when content_mode="full") fields: Optional list of fields to return (e.g. ["id","content_preview","tags"]). None returns all fields. follow: Lineage mode — "latest" resolves each result to its current version, "active" excludes superseded memories, "full_history" expands supersession chains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
metadata_filtersNo
limitNo
offsetNo
date_fromNo
date_toNo
tags_anyNo
tags_allNo
tags_noneNo
sort_by_importanceNo
content_modeNopreview
preview_charsNo
fieldsNo
followNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses default behavior (compact previews to reduce context usage), and explains content_mode and follow lineage modes. Does not mention idempotency, rate limits, or side effects, but it's a read operation and no annotations are provided. Good detail for a list tool.

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

Conciseness4/5

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

Well-structured with a short summary followed by parameter list. Every sentence is informative. Slightly longer than necessary but not verbose. Front-loaded with purpose and usage hints.

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

Completeness4/5

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

Covers filtering, sorting, pagination, field selection, and lineage. Output schema exists so return format is not required. For a 14-parameter tool, the description is thorough. Could mention output structure briefly but not needed.

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

Parameters5/5

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

Schema description coverage is 0%, but the tool description compensates fully with detailed docstring explaining every parameter, including examples for date_from/to (ISO/relative), tag logic (OR/AND/NOT), and follow modes. Adds value beyond schema types.

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?

Clear verb 'List' and resource 'memories', with explicit filtering options. Differentiates from sibling tools like memory_get by mentioning using it for full content, and from memory_list_compact through content_mode default.

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?

Provides explicit guidance on when to use content_mode='full' and when to use memory_get. Explains default behavior (compact previews) and when to switch. Does not cover when not to use this tool vs all siblings, but the main alternative is named.

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/agentic-box/memora'

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