Skip to main content
Glama

auto_white_balance

Automatically adjust white balance for selected photos in Lightroom Classic to correct color temperature and improve image accuracy.

Instructions

Set white balance to Auto for selected photos or local_ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the auto_white_balance tool handler.
    @mcp.tool()
    async def auto_white_balance(local_ids: list[int] | None = None) -> dict[str, Any]:
        """Set white balance to Auto for selected photos or local_ids."""
        ids = validate_local_ids(local_ids)
        payload = {"local_ids": ids} if ids else {}
        return await _call("develop.auto_white_balance", 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 tool performs a write operation ('Set white balance to Auto') but doesn't mention whether this is reversible, what permissions are required, whether it affects original files or virtual copies, or what the response looks like. For a mutation tool with zero annotation coverage, this is insufficient.

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 that gets straight to the point with zero wasted words. It's appropriately sized for this tool's functionality and front-loads the essential information.

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 that there's an output schema (which reduces the need to describe return values), but no annotations and minimal parameter documentation, the description provides basic functionality but lacks important context about behavioral aspects. For a photo editing tool that modifies image properties, more information about side effects and usage constraints would be helpful.

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

Parameters3/5

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

The description mentions 'local_ids' as a parameter option, which aligns with the single parameter in the schema. However, with 0% schema description coverage, the description doesn't explain what happens when local_ids is null (uses default) versus when an array is provided, or clarify the relationship between 'selected photos' and 'local_ids'. It adds some context but doesn't fully compensate for the schema coverage gap.

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 ('Set white balance to Auto') and the target ('selected photos or local_ids'), providing a specific verb+resource combination. It distinguishes from some siblings like 'auto_tone' by specifying the white balance adjustment, though it doesn't explicitly differentiate from all similar tools.

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 doesn't mention prerequisites, when this operation is appropriate, or what happens if no photos are selected. It simply states what the tool does without contextual usage information.

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