Skip to main content
Glama

create_memory

Create an "On this Day" memory from selected past-date photos, making them appear in Immich's memories feed. Provide the display date, the remembered year, and asset IDs.

Instructions

Create an "on this day" memory from chosen assets. Use this after curating a set of photos from the same past date (e.g. via search_metadata with a date range) to make them show up in Immich's memories feed. Side effect: creates a memory on the server.

Args:
    memory_at: ISO date the memory is shown on (usually today's month and day).
    year: The past year the memory looks back to (required by Immich).
    asset_ids: Assets to include. May be empty, but an empty memory shows nothing.

Returns: JSON with the created memory's id, type, memory_at, the year it
remembers, is_saved, asset_count and a trimmed assets list (id, filename, date).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYes
asset_idsNo
memory_atYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It explicitly discloses the mutation with 'Side effect: creates a memory on the server' and warns that an empty asset list yields an empty memory. However, it omits permission requirements, conflict/duplicate behavior, and reversibility, leaving gaps for a mutation tool.

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?

Efficiently structured with a one-line purpose, a usage workflow sentence, a clean Args list, and a Returns specification. No filler, and the core verb/resource is front-loaded.

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 purpose, usage context, all three parameters, side effects, and the return shape in a compact definition. It omits error handling, permissions, and potential conflicts, but for a creation tool with no annotations it is still notably complete.

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?

The schema has 0% description coverage, but the Args section compensates fully: memory_at is explained as the ISO date shown on, year as the required past year, and asset_ids with the empty-list caveat. This gives the agent everything needed to build correct parameters.

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?

States a specific verb and resource: 'Create an "on this day" memory from chosen assets.' It clearly differentiates from sibling memory tools (list_memories, update_memory, delete_memory) by describing the creation action and the Immich memories feed effect.

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 clear workflow context: 'Use this after curating a set of photos from the same past date (e.g. via search_metadata with a date range).' This tells the agent when to invoke the tool, but it doesn't explicitly state alternatives or when not to use it, so it's not a full 5.

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

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/drolosoft/immich-photo-manager'

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