Skip to main content
Glama

apply_lightroom_preset

Apply Lightroom develop presets to photos using preset UUIDs to automate photo editing workflows and enhance images consistently.

Instructions

Apply a Lightroom develop preset by its UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
preset_uuidYes
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool definition and handler for 'apply_lightroom_preset'. It is decorated with @mcp.tool() and uses the _call helper to communicate with the Lightroom bridge.
    @mcp.tool()
    async def apply_lightroom_preset(
        preset_uuid: str,
        local_ids: list[int] | None = None,
    ) -> dict[str, Any]:
        """Apply a Lightroom develop preset by its UUID."""
        if not preset_uuid:
            raise ValueError("preset_uuid is required")
        ids = validate_local_ids(local_ids)
        payload: dict[str, Any] = {"uuid": preset_uuid}
        if ids:
            payload["local_ids"] = ids
        return await _call("develop.apply_lr_preset", payload)
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. It states the action ('Apply') but doesn't explain what this entails—whether it modifies photo settings, requires specific permissions, affects undo/redo states, or has side effects like creating virtual copies. This leaves significant 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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 coverage, and two parameters (one undocumented), the description is inadequate. It lacks behavioral context, parameter explanations, and usage guidance. Although an output schema exists, the description doesn't address critical aspects like what 'Apply' entails or how to use the tool effectively.

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 schema provides no parameter details. The description only mentions 'UUID' for 'preset_uuid', adding minimal context. It doesn't explain 'local_ids' at all—whether it's for targeting specific photos, handling arrays, or defaulting to null. This fails to compensate for the low schema coverage.

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 ('Apply') and target resource ('Lightroom develop preset by its UUID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'apply_develop_preset' or 'apply_develop_settings', which appear to serve similar functions in the Lightroom 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 like 'apply_develop_preset' or 'apply_develop_settings'. The description lacks context about prerequisites, such as whether a photo must be selected or if the preset must be available locally.

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