Skip to main content
Glama

list_snapshots

Retrieve develop snapshots for active photos in Lightroom Classic to review and manage editing history.

Instructions

List develop snapshots for the active photo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool `list_snapshots` is implemented as an async function decorated with `@mcp.tool()`, which validates input IDs and calls the internal `_call` helper to communicate with the Lightroom plugin.
    @mcp.tool()
    async def list_snapshots(local_ids: list[int] | None = None) -> dict[str, Any]:
        """List develop snapshots for the active photo."""
        ids = validate_local_ids(local_ids)
        payload: dict[str, Any] = {}
        if ids:
            payload["local_ids"] = ids
        return await _call("develop.list_snapshots", payload)
Behavior2/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 mentions listing snapshots but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires specific permissions, what the output format looks like (though an output schema exists), or any rate limits. The description is too minimal to inform the agent about how the tool behaves beyond its basic function.

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 a single, efficient sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes to understanding the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (listing snapshots with a parameter), lack of annotations, and an output schema (which reduces the need to describe return values), the description is incomplete. It covers the basic purpose but misses usage guidelines, parameter details, and behavioral context. The output schema helps, but the description should add more value beyond what structured data provides.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter ('local_ids') with 0% description coverage, and the tool description provides no information about parameters. It doesn't explain what 'local_ids' are, how they relate to snapshots, or when to use them (e.g., for filtering). With low schema coverage and no compensation in the description, this leaves the parameter undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and target resource ('develop snapshots'), with context about scope ('for the active photo'). It distinguishes from siblings like 'create_snapshot' and 'delete_snapshot' by focusing on listing. However, it doesn't specify what 'develop snapshots' are or how they differ from other snapshot types, leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active photo), exclusions, or comparisons to similar tools like 'list_collections' or 'list_develop_presets'. Usage is implied only by the phrase 'for the active photo', but this is insufficient for clear decision-making.

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/4xiomdev/lightroom-classic-mcp'

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