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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Rotate assets

rotate_assets

Apply non-destructive clockwise rotation to selected assets or an entire album to correct orientation issues; original files stay unchanged and edits can be reverted.

Instructions

Apply a non-destructive clockwise rotation to one or more assets. Use this to fix orientation issues. The original file is never modified — rotation is a display transform only. Use revert_asset_edits to undo. Provide EITHER asset_ids OR album_id. Side effect: writes rotation edits to Immich; accumulates with existing rotation.

Args:
    angle: Clockwise degrees, must be a multiple of 90 (90, 180, or 270). Default: 90.
    asset_ids: List of asset UUIDs to rotate. Mutually exclusive with album_id.
    album_id: Rotate all assets in this album. Mutually exclusive with asset_ids.

Returns: JSON with rotated/failed counts and the applied angle.

Input Schema

NameRequiredDescriptionDefault
angleNo
album_idNo
asset_idsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false. The description goes further by explaining that the original file is never modified, that rotation is a display transform, that it writes rotation edits to Immich, and that calls accumulate with existing rotation — a non-obvious state effect that prevents double-rotation mistakes.

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 operation and constraint, then a tidy Args block that earns its space because the schema has no field descriptions. The trailing Returns line is slightly redundant given an output schema exists, but it is one line and not disruptive.

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?

Covers scope, safety model, accumulation side effect, undo alternative, mutual exclusivity, and value constraints for a three-parameter mutation tool. Nothing an agent needs in order to call it correctly is missing, and return values are backed by an output schema.

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 coverage is 0%, so the description carries the full burden and does: angle must be a multiple of 90 with a stated default, asset_ids are UUIDs, album_id rotates all assets in the album, and the two are mutually exclusive. This is exactly the meaning missing from the bare schema.

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 ("Apply a non-destructive clockwise rotation to one or more assets") plus the intent ("fix orientation issues"). That distinguishes it from sibling mutations such as update_asset_metadata and explicitly routes undo behavior to revert_asset_edits.

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 the when (fix orientation issues), the undo path (revert_asset_edits), and an explicit exclusion rule: "Provide EITHER asset_ids OR album_id", with both parameters described as mutually exclusive. An agent can choose call shape without 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