Skip to main content
Glama
Sign In
Lightroom MCP Elite

Lightroom MCP Elite

by baramesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

lightroom_list_develop_presets

List all Develop presets in the Lightroom catalog to identify available options for editing and applying adjustments.

Instructions

List all Lightroom Develop presets available in the catalog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lightroom_list_develop_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. 'List' implies a non-mutating enumeration, which is accurate, but it does not mention return format, ordering, or whether an open catalog is required. There is no contradiction, but rich behavior is not disclosed.

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, front-loaded sentence with no redundant words or filler. Every word earns its place.

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?

For a zero-parameter list operation with an output schema, the description is mostly sufficient; the output schema can explain return values. Still, it leaves ambiguity about whether built-in presets are included and does not address the near-duplicate sibling list_develop_presets.

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 zero parameters and the schema coverage is effectively 100%. The description's 'all' confirms no filtering, which is useful, and the zero-parameter baseline of 4 applies.

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?

Description uses a specific verb ('List') and resource ('Lightroom Develop presets') and scopes the operation to the catalog. However, it does not explicitly distinguish itself from the sibling list_develop_presets or clarify whether it includes both built-in and user presets.

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 given on when to use this tool versus alternatives like list_develop_presets, get_develop_preset, or apply_develop_preset. The phrase 'available in the catalog' implies a read-only enumeration, but there are no explicit when-to-use or when-not-to-use instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools