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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete album

delete_album
Destructive

Remove an unwanted album grouping without deleting its photos; the album is permanently deleted and cannot be undone.

Instructions

Delete an album container. The photos inside are NOT deleted — they remain in the library. Use this to remove unwanted album groupings. Side effect: permanently deletes the album (cannot be undone).

Args:
    album_id: The album's UUID to delete.

Returns: JSON with success, the deleted album's id and album_id.

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": {
      "album_id": "<album_id>"
    },
    "name": "delete_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint, but the description adds genuinely non-obvious behavior: contained photos are preserved and remain in the library, and the album deletion is permanent and irreversible. This containment semantics is the crucial detail an agent cannot infer from structured fields.

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 with the most important fact (photos survive), then scope and side effects. Minor waste: the Args/Returns section largely restates what the schema and output schema already provide, and 'permanently deletes the album' partially repeats the destructive hint.

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 single-parameter destructive tool this covers what matters: what is destroyed, what survives, irreversibility, and argument format. It omits edge cases such as behavior when the album_id does not exist or effects on shared links covering the album.

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 coverage is 0% and the schema only says the parameter is a string. The description clarifies it is the album's UUID, which is meaningful format information beyond the schema, though it does not explain how to obtain one (list_albums/get_album).

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 ('Delete an album container') and immediately distinguishes it from deleting photos, which is the key ambiguity against siblings like delete_assets. An agent can tell exactly what object is being removed.

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?

Says 'Use this to remove unwanted album groupings', which implies the use case but gives no explicit exclusions or named alternatives (e.g., remove_assets_from_album for removing photos only, or update_album for renaming). Usage is implied rather than prescribed.

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