Skip to main content
Glama

get_develop_settings

Retrieve all develop settings for active photos in Lightroom Classic, including exposure, contrast, HSL, tone curve, and effects, to analyze current editing state before making adjustments.

Instructions

Get all ~175 develop settings for the active photo (or first in local_ids).

Returns a settings dict with every slider value: exposure, contrast, HSL, split toning, tone curve, sharpening, noise reduction, effects, etc. Call this before editing to understand the photo's current state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_develop_settings tool is defined as an MCP tool with the @mcp.tool() decorator. It fetches develop settings for a photo by calling the internal `_call` helper.
    @mcp.tool()
    async def get_develop_settings(local_ids: list[int] | None = None) -> dict[str, Any]:
        """Get all ~175 develop settings for the active photo (or first in local_ids).
    
        Returns a settings dict with every slider value: exposure, contrast, HSL,
        split toning, tone curve, sharpening, noise reduction, effects, etc.
        Call this before editing to understand the photo's current state.
        """
        ids = validate_local_ids(local_ids)
        params: dict[str, Any] = {}
        if ids:
            params["local_ids"] = ids
        return await _call("develop.get_settings", params)
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns a 'settings dict' with detailed slider values, which is useful behavioral context. However, it lacks information on permissions, rate limits, or error handling, leaving gaps for a read 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?

The description is appropriately sized and front-loaded, with three sentences that each add value: the first states the purpose, the second details the return format, and the third provides usage guidance, with no wasted words.

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

Completeness4/5

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

Given the tool's complexity (reading many settings), no annotations, and an output schema present, the description is mostly complete. It explains the purpose, return format, and usage context, but could benefit from more behavioral details like error cases or performance notes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage for its one parameter ('local_ids'), but the description compensates by explaining its semantics: it specifies that if 'local_ids' is provided, it uses the first ID, and if not, it defaults to the active photo. This adds meaningful context beyond the schema.

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 clearly states the tool's purpose with specific verbs ('Get all ~175 develop settings') and resources ('for the active photo or first in local_ids'), distinguishing it from siblings like 'get_develop_group_settings' or 'get_local_adjustment_settings' by emphasizing comprehensive coverage of all settings.

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

Usage Guidelines4/5

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

The description provides clear context on when to use it ('Call this before editing to understand the photo's current state'), but does not explicitly mention when not to use it or name alternatives among siblings, such as more targeted tools like 'get_develop_group_settings'.

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