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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get timeline bucket

get_timeline_bucket
Read-only

Fetches all assets in one month bucket returned by get_timeline_buckets, optionally filtered by album, person, tag or favorites, so you can page through a library month by month without searches.

Instructions

The assets of one month bucket from get_timeline_buckets. Use the two tools together to walk a library month by month without expensive searches. Read-only.

Args:
    time_bucket: The bucket key exactly as get_timeline_buckets returned it
        (e.g. '2026-03-01').
    album_id: Only assets in this album.
    person_id: Only assets showing this person.
    tag_id: Only assets carrying this tag.
    is_favorite: If true, only favorites.

Returns: JSON with an assets array; each row has asset_id, date, is_image,
is_favorite, duration, city and country.

Input Schema

NameRequiredDescriptionDefault
tag_idNo
album_idNo
person_idNo
is_favoriteNo
time_bucketYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.2

TDQS

A4.4/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 adds real context beyond them: the bucket key must match exactly what get_timeline_buckets returned, and the response shape is stated. It does not mention pagination, result caps, or whether combining multiple filters narrows results, which are the remaining behavioral unknowns for a list tool.

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 sentence is front-loaded and the Args block is justified because the schema has zero descriptions. The separate 'Read-only.' line duplicates the annotation and the Returns block partly duplicates the output schema, adding mild redundancy.

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 five-parameter filtered list tool with an output schema and read-only annotations, the description supplies what structured data does not: the bucket-key contract, filter meanings, and the two-call workflow. It stops short of covering result limits or pagination, which matters for a tool that can return a month of assets.

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 for all five parameters — time_bucket with an exact-format example, and album_id/person_id/tag_id/is_favorite each described as a narrowing filter. The only gap is that the empty-string/no-filter default and AND-combination of filters are left implicit.

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 resource and scope: 'The assets of one month bucket from get_timeline_buckets.' It names the sibling that produces the bucket key and characterizes the search tools as the expensive alternative, so an agent can distinguish this from get_timeline_buckets and search_explore without opening a schema.

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

Usage Guidelines4/5

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

'Use the two tools together to walk a library month by month without expensive searches' gives a clear usage pattern and implicitly routes the agent away from search tools. It lacks an explicit when-not clause (e.g., don't call for cross-library or arbitrary date queries), so it falls short of a 5.

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