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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Clear asset notes

clear_asset_notes
Destructive

Remove the plugin's review and action notes from selected Immich assets while preserving metadata stored by other apps.

Instructions

Forget the plugin's notes on assets (reviews and actions). Only the plugin's own key is removed; metadata other apps stored stays. Side effect: deletes the notes on the server.

Args:
    asset_ids: The assets to clear.

Returns: JSON with success, how many assets were cleared, and a failed array
of {asset_id, error}. Success is true only when nothing failed.

Input Schema

NameRequiredDescriptionDefault
asset_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds real value beyond them: it names the exact blast radius (plugin key only, third-party metadata preserved), states the effect is server-side deletion, and documents partial-failure semantics in the return value. It does not state whether the deletion is reversible.

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 action and its scope, then a clearly labeled side effect, args, and returns section. Sentences earn their place; only the explicit Args block for a single self-evident parameter is slightly redundant.

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 single-parameter destructive mutation this is close to complete: scope of deletion, persistence of other apps' metadata, and the success/failed-array contract are all covered, and an output schema exists so return detail is optional. The missing piece is any statement about reversibility or permission requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 burden, yet "asset_ids: The assets to clear" only restates the parameter name. It gives no guidance on ID format, whether non-existent or foreign IDs fail, batching limits, or what happens on empty input.

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?

"Forget the plugin's notes on assets (reviews and actions)" states a specific verb and resource, and the following sentence delimits exactly which data is affected versus data written by other apps. This makes it distinguishable from sibling readers like get_asset_notes / get_assets_notes and from update_asset_metadata without opening any 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?

The scope sentence ("only the plugin's own key is removed; metadata other apps stored stays") effectively tells an agent when this is the right tool versus broader metadata operations. It stops short of naming an explicit alternative or stating when not to use it (e.g. when you only want to read or update notes).

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