Skip to main content
Glama
Sign In
immich-photo-manager

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Create memory

create_memory

Create an "on this day" memory from selected past-date photos so they appear in Immich's memories feed. Use it after curating assets from the same month and day.

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

NameRequiredDescriptionDefault
yearYes
asset_idsNo
memory_atYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-destructive write; the description adds real value by naming the side effect ('creates a memory on the server') and warning that an empty asset_ids list produces a memory that shows nothing. It also notes year is required by Immich. Return-format detail overlaps the existing output schema rather than adding behavior.

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?

Purpose and the recommended workflow are front-loaded, then per-argument notes follow. The Returns block is somewhat redundant given an output schema exists, but it is short and the overall structure is easy to scan.

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 three-parameter mutation tool with annotations and an output schema, the description covers purpose, prerequisite workflow, mutation side effect and every parameter. Only the precise datetime format for memory_at is missing, which is a minor gap.

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?

With 0% schema description coverage, the description carries the full burden and mostly does: memory_at is an ISO date (usually today's month/day), year is the past year looked back to and is required by Immich, and asset_ids may be empty with a stated consequence. The exact accepted format for memory_at (date vs datetime) is left slightly ambiguous.

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 uses a specific verb+resource: 'Create an "on this day" memory from chosen assets', and immediately scopes it to Immich's memories feed. This distinguishes it clearly from siblings such as list_memories, update_memory and delete_memory.

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?

It states a concrete workflow condition: use it after curating photos from the same past date, e.g. via search_metadata with a date range. It does not mention update_memory or when to skip creating a memory, so it stops short of explicit exclusions, but the guidance is unambiguous.

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

Deploy Server

Other Tools