Skip to main content
Glama
Sign In
Lightroom MCP Elite

Lightroom MCP Elite

by baramesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

lightroom_copy_develop_settings

Copy all Develop adjustments from one source photo to multiple target photos to ensure consistent edits across a batch.

Instructions

Sync all Develop adjustments from a source photo to multiple target photos.

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": {
      "source_photo_id": "<source_photo_id>",
      "target_photo_ids": "<target_photo_ids>"
    },
    "name": "lightroom_copy_develop_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_photo_idYes
target_photo_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'sync all Develop adjustments' but does not state whether this overwrites existing Develop settings on target photos, whether the operation is reversible, or whether any permissions are required. This is a material gap for a mutating operation.

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?

A single, tight sentence that immediately communicates the core behavior. Every word earns its place, and the source-to-target direction is front-loaded without unnecessary filler.

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?

The description covers the basic operation but omits critical context for an agent: the destructive/overwriting nature of syncing settings, how targets are affected, and any caveats about partial or all adjustments. The output schema reduces the need to describe return values, but the behavioral gaps make this incomplete for safe invocation.

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%, and the description only gives conceptual labels ('source photo' and 'multiple target photos') rather than clarifying how the parameters are structured or used. It adds minimal meaning beyond the raw parameter names, and the schema itself lacks descriptions.

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?

The description states a specific verb ('Sync'), a precise resource ('Develop adjustments'), and a relationship ('from a source photo to multiple target photos'). It clearly distinguishes this from setting specific values or applying a preset, making the tool's role unambiguous.

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

Usage Guidelines3/5

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

The description implies the tool's usage context—copying all Develop adjustments from one photo to many—but it gives no explicit guidance on when to choose this over siblings such as set_develop_settings or apply_develop_preset. There are no alternative comparisons or exclusion criteria.

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