Skip to main content
Glama

get_calendar_heatmap

See how many photos were taken or uploaded each day across a date range, revealing gaps, busy periods, and overall library health without listing assets.

Instructions

How many photos per day, over a date range — the data behind a calendar heatmap. Use this to find gaps (months with nothing), busy periods, or to check a library's health at a glance without listing assets. Immich 3.x answers natively; on Immich 2.x the same shape is built from the timeline (taken dates only), which costs one request per month in the range, so pass the narrowest range that answers the question. Read-only.

Args:
    from_date: ISO date lower bound (e.g. '2026-01-01'). Omit for the server
        default on Immich 3.x; on 2.x an omitted bound means the last 365 days,
        because an open-ended range would walk every month of the library.
    to_date: ISO date upper bound. Omit for the server default.
    heatmap_type: 'Taken' (capture date, default) or 'Upload' (when it reached
        Immich; 3.x only).

Returns: JSON with source ('immich' or 'timeline'), total and a series of
{date, count} for the days that have activity, oldest first (a day missing
from the series had nothing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_dateNo
from_dateNo
heatmap_typeNoTaken

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it succeeds thoroughly. It declares read-only status, explains Immich 3.x vs 2.x behavior, documents request costs, describes defaults for omitted bounds, and clarifies that days missing from the series mean zero activity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average but every sentence earns its place: purpose, use cases, version caveats, parameter details, and return shape. It is front-loaded with the core purpose and progresses logically through args and returns, making the length justified by the complexity.

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?

The description covers everything an agent needs to select and invoke this tool correctly: use cases, version-specific behavior, performance implications, parameter semantics, defaults, and the return structure. Even though an output schema exists, the description's own return description adds useful interpretation, such as oldest-first ordering and how missing days are represented.

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 must fully explain the parameters, and it does. It documents ISO date format with an example, server defaults on each version, the meaning of omitted bounds, and defines heatmap_type values 'Taken' and 'Upload' including version restrictions.

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 opens with a concrete one-sentence definition: 'How many photos per day, over a date range — the data behind a calendar heatmap.' It clearly identifies the queried resource, the aggregation unit, and the date-range scope, and it distinguishes itself from asset-listing tools by framing its use as a health/gap check without listing assets.

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?

The description explicitly says when to use this tool: to find gaps, busy periods, or check library health 'without listing assets.' It also gives strong behavioral guidance for version differences, warns about cost on Immich 2.x, and advises passing the narrowest range that answers the question. No ambiguity remains about when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/drolosoft/immich-photo-manager'

If you have feedback or need assistance with the MCP directory API, please join our Discord server