Skip to main content
Glama
drolosoft

immich-photo-manager

by drolosoft
OverviewSchemaRelated ServersScoreDiscussions
Remote

update_asset_metadata

Update photo asset metadata: set original date, GPS coordinates, description, mark favorite, or set rating. Only specified fields are changed.

Instructions

Update metadata for a specific asset (dates, GPS coordinates, description, etc). Only provided fields are updated — omitted fields are left unchanged.

Args:
    asset_id: The unique ID of the asset.
    date_time_original: ISO 8601 date string (e.g. '2019-07-14T15:23:41.000Z').
    latitude: GPS latitude (-90 to 90).
    longitude: GPS longitude (-180 to 180).
    description: Asset description text.
    is_favorite: Mark as favorite.
    rating: Rating from 1-5, or null for unrated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_idYes
date_time_originalNo
latitudeNo
longitudeNo
descriptionNo
is_favoriteNo
ratingNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses partial update behavior but lacks details on permissions, idempotency, or side effects of updates.

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 concise: one sentence for purpose, one for behavior, then a structured Args list. No redundant or missing words.

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?

With 7 parameters, no annotations, but an output schema exists. The description covers all parameters and partial update behavior, but lacks details on response format or error conditions.

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%, but the description's Args section explains each parameter with examples ('ISO 8601 date string', '-90 to 90', 'Rating from 1-5, or null'), adding significant meaning beyond the 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?

The description clearly states 'Update metadata for a specific asset' and lists the specific fields (dates, GPS coordinates, description, etc.), differentiating from sibling tools like search_metadata or update_album.

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?

The description explicitly says 'Only provided fields are updated — omitted fields are left unchanged', providing clear usage context. However, it does not mention when to avoid using this tool or direct alternatives.

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

Install Server

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