Skip to main content
Glama

apply_develop_preset

Apply named Lightroom Classic presets to photos with customizable parameter adjustments for consistent editing workflows.

Instructions

Apply a named preset with optional parameter overrides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presetYes
local_idsNo
overridesNo
strictNo
clampNo
history_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the apply_develop_preset tool, which merges overrides and applies settings via _apply_validated_settings.
    @mcp.tool()
    async def apply_develop_preset(
        preset: str,
        local_ids: list[int] | None = None,
        overrides: dict[str, Any] | None = None,
        strict: bool = False,
        clamp: bool = True,
        history_name: str | None = None,
    ) -> dict[str, Any]:
        """Apply a named preset with optional parameter overrides."""
        preset_name, settings = merge_preset_overrides(preset, overrides)
        response = await _apply_validated_settings(
            settings,
            local_ids=local_ids,
            strict=strict,
            clamp=clamp,
            history_name=history_name or f"MCP Preset: {preset_name}",
        )
        response["preset"] = preset_name
        return response
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 applies a preset with overrides but doesn't disclose behavioral traits like whether this is a destructive operation, what permissions are needed, how it affects the system, or what happens on failure. The description is minimal and lacks critical context for safe use.

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 and appropriately sized for the information it conveys, though it's under-specified rather than concise.

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 complexity (6 parameters, 0% schema coverage, no annotations) and the presence of an output schema, the description is incomplete. It doesn't explain what the tool does beyond the basic action, leaving gaps in purpose, parameter meaning, and behavioral context. The output schema helps but doesn't compensate for the missing description details.

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 'optional parameter overrides' which hints at the 'overrides' parameter, but doesn't explain the meaning of 'preset', 'local_ids', 'strict', 'clamp', or 'history_name'. With 6 parameters and no schema descriptions, this is inadequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('apply') and resource ('named preset'), but is vague about what 'apply' means in this context and doesn't differentiate from sibling tools like 'apply_develop_settings' or 'apply_lightroom_preset'. It mentions 'optional parameter overrides' which adds some specificity but doesn't clarify the domain or effect.

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 on when to use this tool versus alternatives like 'apply_develop_settings' or 'apply_lightroom_preset'. The description doesn't mention prerequisites, context, or exclusions. Usage is implied only through the tool name and brief description.

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