Skip to main content
Glama
4xiomdev

Lightroom Classic MCP

by 4xiomdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_lightroom_presets

Browse and retrieve all available develop presets in Lightroom Classic, including both built-in options and custom user-created presets.

Instructions

List Lightroom's built-in and user-created develop presets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/lightroom_mcp_custom/server.py:878-881 (handler)
    The tool list_lightroom_presets is defined here, decorated with @mcp.tool(), and calls the underlying bridge command 'develop.list_lr_presets'.
    @mcp.tool()
async def list_lightroom_presets() -> dict[str, Any]:
    """List Lightroom's built-in and user-created develop presets."""
    return await _call("develop.list_lr_presets")

Tool Definition Quality

B3.2/5.0
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 it's a list operation, implying read-only behavior, but does not mention potential side effects, rate limits, authentication needs, or the format of the returned data. This leaves gaps in understanding how the tool behaves in practice.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to understand at a glance.

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 the tool has no parameters, an output schema exists, and annotations are absent, the description is minimally adequate. However, it lacks details on behavioral aspects like error handling or data format, which could be important for an AI agent to use it correctly in context with sibling tools.

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 tool has 0 parameters, and the input schema has 100% description coverage, so no parameter information is needed. The description does not add parameter details, which is appropriate, but it also doesn't compensate for any gaps since there are none. A baseline of 4 is applied as it meets the requirement for a parameterless tool.

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 ('List') and resource ('Lightroom's built-in and user-created develop presets'), making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'list_develop_presets' or 'list_develop_parameters', which could cause confusion about scope.

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 like 'list_develop_presets' or 'apply_develop_preset'. The description lacks context about prerequisites, such as whether Lightroom needs to be active or if specific permissions are required.

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