Skip to main content
Glama

create_snapshot

Save current photo editing adjustments as a named snapshot in Lightroom Classic to preserve specific development stages for comparison or reversion.

Instructions

Create a named develop snapshot for the active photo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The create_snapshot tool handler, decorated with @mcp.tool(), which takes a name and optional local_ids to create a develop snapshot in Lightroom via the _call helper.
    @mcp.tool()
    async def create_snapshot(
        name: str,
        local_ids: list[int] | None = None,
    ) -> dict[str, Any]:
        """Create a named develop snapshot for the active photo."""
        if not name:
            raise ValueError("name is required")
        ids = validate_local_ids(local_ids)
        payload: dict[str, Any] = {"name": name}
        if ids:
            payload["local_ids"] = ids
        return await _call("develop.create_snapshot", payload)
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states 'create' implying a write/mutation operation, but doesn't disclose permissions needed, whether it's destructive, rate limits, or what happens on failure. It lacks details like if the snapshot is persistent, reversible via 'undo', or how it interacts with 'active photo' state.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes directly to 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 a mutation tool with no annotations, 2 parameters (0% schema coverage), and an output schema (which reduces need to describe returns), the description is minimally adequate. It states what the tool does but lacks parameter details, behavioral context, and usage guidelines, leaving gaps for an AI agent to infer correctly.

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 must compensate but adds no parameter information. It doesn't explain what 'name' should be (e.g., format, uniqueness), what 'local_ids' refers to (e.g., specific photo adjustments), or their impact. With 2 parameters (1 required) and no schema descriptions, this is a significant gap.

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 ('create') and resource ('named develop snapshot'), and specifies the target ('for the active photo'). It distinguishes from siblings like 'apply_snapshot' or 'list_snapshots' by focusing on creation. However, it doesn't explicitly differentiate from 'create_virtual_copy', which might be a related creation operation.

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 compare with siblings like 'create_virtual_copy' or 'apply_snapshot'. Usage is implied only by the tool name and context.

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