immich-photo-manager

by drolosoft

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Create album

create_album

Create a new album in Immich and optionally add asset IDs immediately to organize photos into collections.

Instructions

Create a new album, optionally pre-populated with assets. Use this to organize photos into collections. Side effect: creates a new album in Immich.

Args:
    name: Album display name (e.g. 'Roma, Italia', 'Birthday 2024').
    description: Optional album description text.
    asset_ids: Optional list of asset UUIDs to add immediately on creation.

Returns: JSON with the new album's id, name, and asset count.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_album"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`asset_ids`	No
`description`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write nature is known; the description's 'Side effect: creates a new album in Immich' largely restates that. It does add one useful behavioral note – that asset_ids are attached immediately at creation – but omits permissions, failure behavior for invalid asset UUIDs, and any duplicate-name handling.

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?

Front-loaded summary sentence followed by a compact Args block; every entry is short and readable. The 'Returns' block is redundant with the existing output schema, and the 'Side effect' clause adds little, which keeps it from a 5.

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?

With annotations covering the safety profile and an output schema covering the return shape, this description only needs to explain intent and parameters, which it does. Remaining gaps are minor behavioral details rather than anything that would cause a mis-call.

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%, so the description carries the full burden and mostly discharges it: name is illustrated with concrete examples, description is flagged optional, and asset_ids is explained as a list of asset UUIDs applied immediately. Only edge-case semantics (max list size, invalid ID handling) are missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a new album') plus a scope qualifier ('optionally pre-populated with assets') and a use case ('organize photos into collections'). It does not explicitly name sibling alternatives such as add_assets_to_album or update_album, so the agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this to organize photos into collections' gives a broad usage context, but there is no explicit when-to-use vs when-not guidance and no mention of the obvious alternative path (create empty album, then call add_assets_to_album). Usage is implied rather than directed.

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

Deploy Server