Skip to main content
Glama

set_develop_group

Apply partial updates to specific develop parameter groups in Lightroom Classic for targeted photo adjustments.

Instructions

Apply a partial update to one develop parameter group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYes
valuesYes
local_idsNo
strictNo
clampNo
history_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the set_develop_group tool handler.
    async def set_develop_group(
        group: str,
        values: dict[str, Any],
        local_ids: list[int] | None = None,
        strict: bool = False,
        clamp: bool = True,
        history_name: str | None = None,
    ) -> dict[str, Any]:
        """Apply a partial update to one develop parameter group."""
        canonical, scoped_values = validate_group_values(group, values)
        response = await _apply_validated_settings(
            scoped_values,
            local_ids=local_ids,
            strict=strict,
            clamp=clamp,
            history_name=history_name or f"MCP Group: {canonical}",
        )
        response["group"] = canonical
        return response
  • Registration of the set_develop_group tool via @mcp.tool() decorator.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'partial update' implies mutation, it doesn't specify whether this requires specific permissions, what happens to unspecified parameters in the group, whether changes are reversible, or any side effects. The description lacks critical behavioral context 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 target, 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 6 parameters (2 required), 0% schema description coverage, no annotations, and an output schema (which helps but isn't described), the description is inadequate. It doesn't explain parameter meanings, behavioral implications, or usage context, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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 parameters like 'group', 'values', 'local_ids', 'strict', 'clamp', and 'history_name' are undocumented in the schema. The description mentions 'develop parameter group' which hints at the 'group' parameter, but provides no explanation of what 'values' should contain, what 'clamp' or 'strict' do, or the purpose of 'local_ids' and 'history_name'. It fails to compensate for the schema's lack of documentation.

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 a partial update') and the target ('one develop parameter group'), which is specific and actionable. However, it doesn't distinguish this tool from sibling tools like 'set_develop_param' or 'apply_develop_settings', which appear to be related operations on develop parameters.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools related to develop operations (e.g., 'set_develop_param', 'apply_develop_settings', 'apply_develop_preset'), there's no indication of when this partial update to a group is preferred over other methods.

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