Skip to main content
Glama

delete_memory

Remove a specific memory by ID when it is outdated, incorrect, or user requests deletion.

Instructions

Remove a specific memory when it is no longer relevant, was stored in error, or user requests deletion.

When to Use

  • User requests deletion ('Forget what I said about X')

  • Old version redundant after update

  • Something stored by mistake

  • User explicitly asks to 'forget' or 'delete' specific information

Privacy

Honor all deletion requests promptly. User privacy is paramount.

Cleanup Pattern

After post-response storage evaluation, if a memory is found to be:

  • Redundant with newly updated version

  • Incorrectly stored

  • No longer relevant

→ Delete the old/incorrect memory to maintain clean memory store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMemory ID to delete.
Behavior3/5

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

No annotations provided, so description carries full burden. It covers privacy and cleanup patterns but does not mention irreversibility, authentication, or side effects.

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 clear headings. Front-loaded with purpose, then guidelines, privacy, and cleanup. Each section adds value, though could be slightly more concise.

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

Completeness3/5

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

Covers main use cases but lacks explanation of return values or error handling (e.g., invalid id). Adequate for a simple deletion tool but incomplete for edge cases.

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

Parameters3/5

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

Only one parameter 'id' with schema description already clear. The description adds no extra meaning beyond schema, and coverage is 100%.

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 description clearly states the verb 'Remove' and the resource 'specific memory', distinguishing it from siblings like delete_all_memories. It also specifies contexts where deletion is appropriate.

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 'When to Use' section provides specific scenarios such as user requests deletion, redundancy, or error. It implicitly excludes other operations but does not explicitly name alternatives.

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/JoeXie/remember-me'

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