Skip to main content
Glama

select_mask

Select an existing mask in Lightroom Classic by its numeric ID to apply targeted adjustments to specific areas of a photo.

Instructions

Select an existing mask by its numeric ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mask_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'select_mask' tool handler, registered with @mcp.tool(), which selects an existing mask by its numeric ID.
    @mcp.tool()
    async def select_mask(mask_id: int) -> dict[str, Any]:
        """Select an existing mask by its numeric ID."""
        return await _call("masks.select_mask", {"mask_id": mask_id})
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 action is to 'select' a mask, implying a read or activation operation, but doesn't disclose behavioral traits like whether this changes application state, requires specific permissions, or has side effects (e.g., visual feedback). For a tool with zero annotation coverage, this leaves significant gaps in understanding its impact.

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 zero waste. It is front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes directly to understanding the tool's purpose.

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 has an output schema (which handles return values), the description's main gaps are in usage guidelines and behavioral transparency. With no annotations and low parameter coverage, it provides minimal context beyond the basic action. For a simple selection tool, it's adequate but lacks depth on integration and effects.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by specifying that 'mask_id' is a 'numeric ID', which clarifies the parameter type beyond the schema's 'integer'. However, it doesn't explain what a mask ID represents, how to obtain it, or valid ranges, leaving the parameter only partially documented.

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 ('Select') and resource ('an existing mask'), specifying it's done 'by its numeric ID'. It distinguishes from sibling 'select_mask_tool' by focusing on selection by ID rather than tool activation. However, it doesn't explicitly differentiate from other mask-related tools like 'create_ai_mask' or 'invert_mask' beyond the selection aspect.

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. It doesn't mention prerequisites (e.g., needing an existing mask ID), nor does it contrast with similar tools like 'select_mask_tool' or explain its role in a workflow. The description assumes context without providing usage context.

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