Lightroom Classic MCP

Overview Schema Source Related Servers Discussions Admin

create_virtual_copy

Create virtual copies of photos in Lightroom Classic to experiment with edits while preserving original files. Use this tool to apply different adjustments to the same image without duplicating storage.

Instructions

Create virtual copies of selected photos or specific local_ids.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_virtual_copy"
  }
}

Input Schema

Name	Required	Description	Default
`local_ids`	No

Output Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/lightroom_mcp_custom/server.py:848-855 (handler)

The create_virtual_copy tool handler, decorated with @mcp.tool(), which validates local IDs and calls the underlying Lightroom catalog API.

@mcp.tool()
async def create_virtual_copy(local_ids: list[int] | None = None) -> dict[str, Any]:
    """Create virtual copies of selected photos or specific local_ids."""
    ids = validate_local_ids(local_ids)
    payload: dict[str, Any] = {}
    if ids:
        payload["local_ids"] = ids
    return await _call("catalog.create_virtual_copy", payload)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Mar 19, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't specify whether this requires specific permissions, what happens to the original photos, whether the operation is reversible, or what the virtual copies actually are. This leaves significant behavioral gaps for a mutation tool.

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 zero wasted words. It's appropriately sized for a tool with one parameter and gets straight to the point without unnecessary elaboration.

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?

For a mutation tool with no annotations, 0% schema description coverage, and rich sibling tools (including other creation operations), the description is inadequate. It doesn't explain what virtual copies are, how they differ from other photo derivatives, what the output contains, or the operational context needed. The existence of an output schema helps but doesn't compensate for these fundamental gaps.

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 mentions 'local_ids' but doesn't explain what they are, how to obtain them, or what happens when they're null (which is the default). The description adds minimal semantic value beyond what's inferable from the parameter name itself.

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 virtual copies') and the target resource ('selected photos or specific local_ids'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from potential sibling operations like 'create_snapshot' or 'apply_snapshot' that might also create derivative versions of photos.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing selected photos first), nor does it explain what 'virtual copies' are compared to other operations like snapshots or presets available in the sibling tool list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server