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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List assets

list_assets
Read-only

Browse and filter photo or video assets by favorite, archived, or trashed status and media type, with pagination; no search query required.

Instructions

List assets with simple filters (no search query needed). Use this to browse the library by status (favorites, archived, trashed) or type. For finding specific content, use search_metadata (structured) or search_smart (visual AI). Read-only.

Args:
    is_favorite: true = only favorites, false = only non-favorites, omit = all.
    is_archived: true = only archived, false = only non-archived, omit = all.
    is_trashed: true = only trashed items; false/omit = active library (Immich never mixes both).
    asset_type: 'IMAGE' or 'VIDEO'. Omit for both.
    page: Page number, starting from 1 (default 1).
    size: Results per page (1-200, default 50).

Returns: JSON with total count, current page, and assets array with IDs, filenames, dates, and types.

Input Schema

NameRequiredDescriptionDefault
pageNo
sizeNo
asset_typeNo
is_trashedNo
is_archivedNo
is_favoriteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

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, so 'Read-only' is mostly redundant, but the description adds genuinely new behavior: the three-state filter semantics and the constraint that trashed and active items are never returned together ('Immich never mixes both'). Pagination defaults and the return shape are also disclosed, though the Returns line partly duplicates the existing output schema.

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?

The routing guidance is front-loaded in the opening sentences, followed by a scannable per-argument block with no filler prose. Minor waste remains: 'Read-only.' restates the annotations and the Returns sentence overlaps with the output schema, so it is not maximally tight.

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?

A six-parameter, zero-required list tool with an output schema is fully covered here: purpose, alternatives, every parameter's semantics, and pagination behavior are all present. Nothing an agent needs in order to select and call it correctly is missing.

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: each of the six parameters is explained with its default, its tri-state meaning for the boolean filters, the valid values ('IMAGE' or 'VIDEO'), and the 1-200 range for size. This adds substantial meaning the bare schema (types and defaults only) does not convey.

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 ('List assets with simple filters') plus the critical scoping fact that no search query is required. The follow-up sentence names the exact sibling tools (search_metadata, search_smart) so an agent can distinguish browsing from searching without inspecting 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?

Explicitly separates when to use this tool (browsing the library by status or type) from when not to ('For finding specific content, use search_metadata (structured) or search_smart (visual AI)'). Both alternatives and the condition selecting them are named, leaving nothing to inference.

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