Skip to main content
Glama

delete_snapshot

Remove unwanted develop snapshots from Lightroom Classic to manage photo editing history and optimize catalog organization by specifying snapshot IDs.

Instructions

Delete a develop snapshot by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
snapshot_idYes
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `delete_snapshot` tool handler, which validates the snapshot ID and calls the underlying `develop.delete_snapshot` Lightroom method.
    async def delete_snapshot(
        snapshot_id: str,
        local_ids: list[int] | None = None,
    ) -> dict[str, Any]:
        """Delete a develop snapshot by its ID."""
        if not snapshot_id:
            raise ValueError("snapshot_id is required")
        ids = validate_local_ids(local_ids)
        payload: dict[str, Any] = {"snapshot_id": snapshot_id}
        if ids:
            payload["local_ids"] = ids
        return await _call("develop.delete_snapshot", payload)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool deletes a snapshot, implying a destructive mutation, but doesn't disclose critical behavioral traits such as whether deletion is permanent, requires specific permissions, has side effects (e.g., on related data), or provides confirmation feedback. This leaves significant gaps for safe invocation.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse, which is ideal for conciseness.

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

Completeness2/5

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

Given the tool's complexity (destructive operation with 2 parameters, 0% schema coverage, no annotations, but with an output schema), the description is incomplete. It lacks behavioral details, parameter explanations, and usage context, relying too heavily on the output schema to compensate, which isn't sufficient for safe and effective use.

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. It only mentions 'snapshot_id', ignoring the second parameter 'local_ids' entirely. No additional meaning is provided for either parameter, such as format examples or how 'local_ids' relates to the deletion process, failing to address the coverage 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 ('Delete') and the resource ('a develop snapshot by its ID'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'delete_collection', but the resource specificity ('develop snapshot') provides adequate clarity for the given context.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing snapshot), exclusions, or related tools like 'create_snapshot' or 'list_snapshots' from the sibling list, leaving the agent to infer usage 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