Skip to main content
Glama
arunkumars-mf

mem0-agent-memory

import_memories

Restore, migrate, or share AI agent memories by importing a JSON export. Provide the file path and optionally override the user/agent or skip existing memories.

Instructions

Import memories from exported JSON file.

REQUIRED: 'file_path' - path to the JSON export file OPTIONAL: 'user_id' OR 'agent_id' - override the user/agent from the export file OPTIONAL: 'skip_existing' - if True, skip memories that already exist (default: True) OPTIONAL: 'infer' - use LLM processing during import (default: False for speed)

Imports memories from a JSON file created by export_memories tool. Useful for backup restoration, migration between backends, or sharing memory sets.

Examples:

  • Import from backup: {"file_path": ".mem0/exports/memories_john_20250113.json"}

  • Import to different user: {"file_path": "export.json", "user_id": "jane"}

  • Force reimport: {"file_path": "export.json", "skip_existing": false}

Returns: Import summary with success/failure counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inferNo
user_idNo
verboseNo
agent_idNo
file_pathYes
skip_existingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.3.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and covers meaningful details: skip_existing semantics, infer defaulting to false for speed, user/agent override, and a return summary. It does not discuss potential side effects when skip_existing is false, but the additive bulk-import nature is reasonably clear.

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?

The structure is clearly front-loaded with REQUIRED/OPTIONAL sections followed by examples and return info. Minor redundancy appears because 'Import memories from exported JSON file' is restated later as 'Imports memories from a JSON file created by export_memories tool,' so it is not maximally tight.

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?

For a file-based bulk import with an output schema, the description covers purpose, source format, parameter semantics, use cases, and examples. The undocumented verbose parameter is the main omission, but it is a minor behavioral flag and likely self-explanatory.

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 description coverage is 0%, and the description compensates well by explaining file_path, user_id/agent_id, skip_existing, and infer with defaults and examples. The only schema parameter not mentioned is verbose, which leaves a small but real gap.

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?

The opening line uses a specific verb ('Import') and resource ('memories') and identifies the source format ('exported JSON file'). It clearly differentiates from siblings like export_memories or store_memory by framing this as a bulk file-based restore operation.

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?

The description names the companion tool (export_memories) and lists concrete scenarios: backup restoration, migration between backends, and sharing memory sets. It does not explicitly state when to avoid using it, such as preferring store_memory for single additions, so it stops short of full when/when-not routing.

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

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/arunkumars-mf/mem0-agent-memory'

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