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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get album thumbnails

get_album_thumbnails
Read-only

Retrieve base64-encoded photo thumbnails from an Immich album to build visual HTML galleries, with selectable thumbnail or preview size and a result limit.

Instructions

Get base64-encoded thumbnails for photos in an album. Use this to generate visual HTML galleries from an existing album. For thumbnails from search results (no album), use get_thumbnails_batch instead. Read-only.

Args:
    album_id: The album's UUID.
    size: 'thumbnail' (250px) or 'preview' (1440px). Default: 'thumbnail'.
    limit: Max thumbnails to return (1-50, default 20).

Returns: JSON with album info and thumbnails array (each with asset_id, base64 data, filename, date).

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_thumbnails"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNothumbnail
limitNo
album_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/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, and the description restates read-only, so safety adds nothing new. However, it does disclose the return shape (album info plus thumbnails array with base64 data), which signals potentially heavy payloads, and gives the default and cap on count (20, max 50). It stops short of noting payload-size or rate-limit implications of base64 blobs.

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 purpose sentence followed by routing guidance and a compact Args block; almost every line earns its place. The trailing 'Read-only' sentence duplicates the readOnlyHint annotation, and the Returns block partially duplicates the existing output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with an output schema, the description covers purpose, alternative routing, all parameter semantics, and the response shape. Nothing materially needed for correct invocation is absent.

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?

Schema description coverage is 0%, so the description carries the full burden and does so: album_id is identified as a UUID, size is given both allowed values with pixel meanings and a default, and limit is given its range (1-50) and default of 20. Nothing an agent needs to construct a call is missing.

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 (base64-encoded thumbnails for photos in an album) and immediately distinguishes itself from get_thumbnails_batch by noting the batch variant is for search results with no album. An agent can identify this tool's scope without opening the 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?

Gives an explicit use case (generate visual HTML galleries from an existing album) and an explicit alternative with the selecting condition (search results without an album -> get_thumbnails_batch). This is the when/when-not/alternative pattern fully realized.

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