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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get timeline buckets

get_timeline_buckets
Read-only

Map your photo library month by month with asset counts to find gaps, busy periods, or navigate large collections before fetching assets. Supports album, person, tag, and favorite filters.

Instructions

Month-by-month map of the library: one bucket per month with its asset count. Use this before fetching assets — it shows in one cheap call which months hold photos and how many, ideal for finding gaps, busy periods, or navigating a large library without paging through everything. Read-only.

Args:
    album_id: Only count assets in this album.
    person_id: Only count assets showing this person.
    tag_id: Only count assets carrying this tag.
    is_favorite: If true, only count favorites.
    order: 'desc' for newest month first (the default), 'asc' for oldest first.

Returns: JSON with total_buckets and a buckets array of {timeBucket, count},
newest month first unless order='asc'.

Input Schema

NameRequiredDescriptionDefault
orderNo
tag_idNo
album_idNo
person_idNo
is_favoriteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.2

TDQS

A4.6/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's 'Read-only.' line just restates that. What it adds beyond annotations is cost and shape: 'one cheap call,' the default ordering, and the returned {timeBucket, count} structure. It does not discuss authorization scoping or limits on bucket granularity, but the behavioral picture is otherwise solid for a read-only aggregator.

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 purpose and the pre-fetch guidance are front-loaded in the first two sentences, which is the right ordering. The Args/Returns docstring block is efficient but partly redundant with the input and output schemas. Nothing is padded, but the structure is more verbose than the task requires.

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 five-parameter, zero-required, read-only aggregation tool with an output schema present, the description covers purpose, usage context, every filter's meaning, ordering default, and the response shape. An agent has everything it needs to choose and invoke this correctly without opening the schema.

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%, so the description carries full responsibility, and it does document all five parameters with filtering semantics ('Only count assets in this album/person/tag', favorites-only, and direction). It also resolves an ambiguity the schema leaves open by declaring 'desc' the default while the schema shows an empty-string default for order. It stops short of specifying expected id formats or behavior when multiple filters are combined.

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 description gives a concrete verb and resource shape: a 'month-by-month map of the library' returning 'one bucket per month with its asset count.' It also implicitly distinguishes itself from asset-listing siblings by framing itself as an aggregate overview rather than an asset fetch. The only gap is that it never names the close sibling get_timeline_bucket (singular), but the aggregate framing still makes the tool's identity unmistakable.

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 explicitly states when to use it ('Use this before fetching assets') and why, and names the alternative it replaces ('navigating a large library without paging through everything'). It also lists concrete use cases: finding gaps, busy periods, or orienting in a large library. That is a when/when-not/alternative statement rather than a vague suggestion.

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