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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get download info

get_download_info
Read-only

Estimate the ZIP size and archive count for an album or selected assets before downloading, so you can warn users about storage needs and decide whether to proceed. Read-only.

Instructions

How big the zip of an album or selection would be, BEFORE building it. Use this to warn the user about the size (originals and videos add up fast) and then decide whether to call download_archive. Read-only.

Args:
    album_id: Size the whole album.
    asset_ids: Or size just these assets.

Returns: JSON with total_size_mb, asset_count and the number of archives
Immich would split the download into.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
album_idNo
asset_idsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true), so the 'Read-only' line is largely redundant. The description does add genuine behavior beyond the annotations: that large originals/videos inflate size, and that Immich may split the download into multiple archives. It stops short of noting any rate limits or cost of computing the size, but it is meaningfully richer than the annotations.

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 core 'what' before the args and returns sections, and no filler sentences. The Returns block partially restates information the output schema already carries, which is mild redundancy rather than bloat.

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

Completeness3/5

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

An output schema exists, so return values need not be spelled out, and the description is otherwise good on purpose and workflow. The notable gap is the undefined interaction between the two optional parameters, which an agent needs in order to call this correctly on a partial selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 burden, and it does explain each parameter's intent ('Size the whole album' vs 'Or size just these assets'). However, neither parameter is required, so the critical question of what happens if both are supplied, if neither is supplied, or whether they are mutually exclusive is left unanswered.

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: estimate the zip size of an album or selection 'BEFORE building it'. The contrast with the sibling download_archive (which actually builds it) is made explicit in the first sentence, so an agent can distinguish them 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?

Gives a concrete use case (warn the user about size, since 'originals and videos add up fast') and a concrete decision point (then decide whether to call download_archive). This is explicit when-to-use plus a named alternative, not just implied context.

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