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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get album

get_album
Read-only

Retrieve full details for a specific album, including metadata, all asset IDs, and recognized people, to inspect album contents or prepare further operations. Read-only.

Instructions

Get full details for a specific album including all its asset IDs. Use this to inspect album contents or retrieve asset IDs for further operations (thumbnails, metadata, rotation). For listing all albums, use list_albums instead. Read-only.

Args:
    album_id: The album's UUID (from list_albums or create_album).

Returns: JSON with album metadata, a flat list of all asset_ids, and an assets array
(id, filename, type, date, recognized people) so "who appears in this album / who
repeats" can be answered without further calls.

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": "get_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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the 'Read-only' sentence is mostly redundant. The description does add real behavioral context beyond annotations: the response is exhaustive ('a flat list of all asset_ids'), so no pagination or follow-up calls are needed, and downstream operations (thumbnails, metadata, rotation) are named. It still does not state error behavior for an invalid album_id.

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, alternative, argument, and return value are ordered and front-loaded, with no filler sentences. The Args/Returns blocks are slightly verbose and partly restate what the output schema could carry, but they earn their place given 0% schema coverage.

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 read tool this covers purpose, provenance of the ID, the alternative tool, and the return shape. The Returns paragraph overlaps with the existing output schema, so it is not maximally efficient, but nothing an agent needs to call it correctly is missing.

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 must carry the parameter meaning, and it does: album_id is described as a UUID plus where to obtain it ('from list_albums or create_album'). No format example or failure mode is given for a malformed ID, which keeps it below a 5.

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 first sentence names a specific verb and resource ('Get full details for a specific album') and states the scope of the payload ('all its asset IDs'). It explicitly contrasts itself with the sibling 'list_albums', so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

It gives positive usage guidance ('inspect album contents or retrieve asset IDs for further operations') and names the alternative with the condition that selects it ('For listing all albums, use list_albums instead'). This is an explicit when-to-use / when-to-use-something-else split.

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