Skip to main content
Glama
4xiomdev

Lightroom Classic MCP

by 4xiomdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_active_photo

Retrieve the currently selected photo in Lightroom Classic for editing or workflow automation.

Instructions

Get the active Lightroom photo in the current selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/lightroom_mcp_custom/server.py:231-234 (handler)
    The get_active_photo tool is defined as an MCP tool using the @mcp.tool() decorator and calls the underlying Lightroom bridge command 'catalog.get_active_photo'.
    @mcp.tool()
async def get_active_photo() -> dict[str, Any]:
    """Get the active Lightroom photo in the current selection."""
    return await _call("catalog.get_active_photo")

Tool Definition Quality

B3.3/5.0
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 a read operation ('Get'), which implies non-destructive behavior, but doesn't disclose details like error handling (e.g., what happens if no photo is active), permissions needed, or rate limits. It adds basic context about the selection but lacks richer behavioral traits.

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 front-loads the key action and resource. Every word earns its place with no waste, making it highly concise and well-structured for quick understanding.

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 0 parameters, 100% schema coverage, and an output schema exists (so return values are documented elsewhere), the description is reasonably complete. It specifies the resource and context ('active Lightroom photo in the current selection'), which is adequate for this simple tool. However, it could benefit from more behavioral details given no annotations.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description doesn't add param semantics, but with no params, the baseline is 4 as it's complete by default. No compensation is required.

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 verb 'Get' and the resource 'active Lightroom photo', specifying it's from 'the current selection'. It distinguishes from siblings like 'get_selected_photos' (plural) and 'get_active_photo_file' (file vs. photo). However, it doesn't fully differentiate from potential similar tools like 'get_selected_photos' in terms of scope, so it's not a perfect 5.

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 minimal guidance by mentioning 'in the current selection', which implies usage when a selection exists, but it doesn't specify when to use this vs. alternatives like 'get_selected_photos' or 'get_active_photo_file', nor does it mention prerequisites or exclusions. No explicit alternatives or context is provided.

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