Skip to main content
Glama

list_develop_presets

Retrieve built-in Lightroom Classic editing presets for quick application to photos, enabling efficient batch processing and consistent styling across images.

Instructions

List built-in editing presets that can be applied in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main MCP tool handler function for `list_develop_presets`. It delegates the data retrieval to `list_preset_descriptions` and formats the output.
    async def list_develop_presets() -> dict[str, Any]:
        """List built-in editing presets that can be applied in one call."""
        presets = list_preset_descriptions()
        return {
            "count": len(presets),
            "presets": presets,
  • Registration of the `list_develop_presets` tool using the `@mcp.tool()` decorator.
    @mcp.tool()
    async def list_develop_presets() -> dict[str, Any]:
  • Helper function that constructs the list of preset descriptions by accessing `DEVELOP_PRESETS` and `PRESET_DESCRIPTIONS`.
    def list_preset_descriptions() -> list[dict[str, Any]]:
        out: list[dict[str, Any]] = []
        for name in sorted(DEVELOP_PRESETS):
            out.append(
                {
                    "preset": name,
                    "description": PRESET_DESCRIPTIONS.get(name),
                    "parameter_count": len(DEVELOP_PRESETS[name]),
                    "parameters": sorted(DEVELOP_PRESETS[name]),
                }
            )
        return out
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 mentions that presets 'can be applied in one call,' hinting at a read-only operation, but fails to detail critical aspects like permissions, rate limits, output format, or pagination. This leaves significant gaps for a tool with no annotation support.

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 any fluff or repetition. It is front-loaded and every word contributes to understanding, making it highly concise and well-structured.

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's simplicity (0 parameters, output schema exists), the description is adequate but incomplete. It lacks behavioral details like output structure or usage context, which are important even with an output schema. The presence of an output schema reduces the burden, but the description should still cover more operational context.

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 schema description coverage is 100%, so no parameter information is needed. The description appropriately avoids redundant details, earning a baseline score of 4 for not overloading with unnecessary content.

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 ('List') and resource ('built-in editing presets'), with the additional context that these presets 'can be applied in one call.' However, it does not explicitly differentiate from sibling tools like 'list_lightroom_presets' or 'apply_develop_preset,' which slightly reduces clarity.

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 no guidance on when to use this tool versus alternatives, such as 'list_lightroom_presets' or 'apply_develop_preset.' It lacks context about prerequisites, timing, or exclusions, leaving usage entirely implied.

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