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

immich-photo-manager

by drolosoft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get asset info

get_asset_info
Read-only

Retrieve full metadata for a single Immich asset by UUID, including EXIF, GPS, camera details, dates, dimensions, file size, and owner; optionally include review notes and recorded actions.

Instructions

Get full metadata for a single asset. Use this when you need EXIF details, GPS coordinates, camera info, or file properties for a known asset ID. For finding assets, use search_metadata or search_smart instead. Read-only.

Args:
    asset_id: The asset's UUID (from search results, album listings, or list_assets).
    with_notes: Also include the plugin's notes on the asset (past review
        verdicts and recorded actions, see get_asset_notes). One extra request.

Returns: JSON with EXIF data, GPS, dates, dimensions, file size, camera
make/model, and owner; plus a `notes` object (reviews and actions) when
with_notes is true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset_id": "<asset_id>"
    },
    "name": "get_asset_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYes
with_notesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.2
    • addedInput schema / properties / with_notes
      Added value: +{
+  "default": false,
+  "title": "With Notes",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

A5/5.0
Behavior5/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 reinforces rather than contradicts that. It adds genuinely new behavioral facts: with_notes triggers 'One extra request' (a cost/latency signal not present in any structured field), and the return contents are enumerated so the agent knows what it will get back. This is meaningful context beyond the annotation set.

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?

Front-loaded with purpose and the when/when-not routing, then structured into Args and Returns blocks with no filler. The only slightly redundant element is 'Read-only', which the annotations already state, but it is a single clause in an otherwise tight definition.

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?

For a two-parameter read tool with an output schema, everything an agent needs is present: purpose, alternative routing, ID provenance, the optional flag's semantics and cost, and a return-value summary. Nothing material is left to inference, and the sibling get_asset_notes is cross-referenced for the notes case.

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 carry the full burden and it does: asset_id is defined as the UUID with concrete provenance (from search results, album listings, or list_assets), and with_notes is explained as plugin notes containing past review verdicts and recorded actions, plus its extra-request cost. Both parameters gain meaning that the bare schema does not supply.

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 ('Get full metadata for a single asset') and immediately scopes it with the concrete field families returned (EXIF, GPS, camera, file properties). It explicitly distinguishes itself from lookup siblings search_metadata and search_smart, so an agent can separate retrieval-by-ID from discovery 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 Guidelines5/5

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

Gives both the when-to-use condition ('when you need EXIF details, GPS coordinates, camera info, or file properties for a known asset ID') and the when-not-to-use routing ('For finding assets, use search_metadata or search_smart instead'). The prerequisite of already knowing an asset ID is explicit, which is the key selection boundary against the search tools.

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