Skip to main content
Glama

get_develop_group_settings

Retrieve specific develop group settings in Lightroom Classic to apply consistent photo adjustments across multiple images.

Instructions

Get only the settings for one named develop group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYes
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that retrieves settings for a specific Lightroom develop group.
    async def get_develop_group_settings(
        group: str,
        local_ids: list[int] | None = None,
    ) -> dict[str, Any]:
        """Get only the settings for one named develop group."""
        canonical, parameters = get_group_parameters(group)
        response = await get_develop_settings(local_ids=local_ids)
        settings = response.get("settings") or {}
        if not isinstance(settings, dict):
            raise RuntimeError("Lightroom returned an invalid settings payload")
    
        grouped = {name: settings[name] for name in parameters if name in settings}
        missing = [name for name in parameters if name not in grouped]
        return {
            "group": canonical,
            "local_id": response.get("local_id"),
            "parameter_count": len(parameters),
            "settings": grouped,
            "missing_parameters": missing,
        }
  • Tool registration for get_develop_group_settings.
    @mcp.tool()
    async def get_develop_group_settings(
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. It states it's a read operation ('Get'), implying non-destructive behavior, but doesn't cover aspects like authentication needs, rate limits, error handling, or what the output contains (though an output schema exists). This leaves significant gaps for a tool with no annotation support.

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, clear sentence with zero waste. It's front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (2 parameters, no nested objects) and the presence of an output schema (which handles return values), the description is somewhat complete for basic understanding. However, with no annotations and poor parameter documentation, it lacks depth for safe and effective use, especially compared to siblings like 'get_develop_settings'.

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%, meaning parameters are undocumented in the schema. The description mentions 'one named develop group', which hints at the 'group' parameter, but doesn't explain the 'local_ids' parameter at all. It adds minimal value beyond the schema, failing to compensate for the low 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 ('Get') and resource ('settings for one named develop group'), making the purpose specific and understandable. However, it doesn't distinguish this tool from similar siblings like 'get_develop_settings' or 'list_develop_groups', which limits its differentiation.

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. The description lacks context about prerequisites, such as needing to know the group name from 'list_develop_groups', or when to use this over 'get_develop_settings' for broader settings retrieval.

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