Skip to main content
Glama

list_develop_groups

Retrieve grouped develop parameter sets to apply consistent edits across multiple photos in Lightroom Classic.

Instructions

List grouped develop parameter sets for faster targeted edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function for 'list_develop_groups' which calls the helper function list_group_descriptions.
    @mcp.tool()
    async def list_develop_groups() -> dict[str, Any]:
        """List grouped develop parameter sets for faster targeted edits."""
        groups = list_group_descriptions()
        return {
            "count": len(groups),
            "groups": groups,
        }
  • Helper function that generates the list of develop group descriptions used by the 'list_develop_groups' tool.
    def list_group_descriptions() -> list[dict[str, Any]]:
        out: list[dict[str, Any]] = []
        for name in sorted(DEVELOP_GROUPS):
            params = DEVELOP_GROUPS[name]
            out.append(
                {
                    "group": name,
                    "parameter_count": len(params),
                    "parameters": [describe_parameter(param) for param in params],
                }
            )
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 this is a list operation, implying it's read-only and non-destructive, but doesn't disclose behavioral traits like whether it requires specific permissions, how results are formatted, if there's pagination, or what 'grouped' means operationally (e.g., by preset type or user-defined). The phrase 'faster targeted edits' hints at efficiency but lacks concrete details.

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 core action ('List grouped develop parameter sets') and adds value with the purpose ('for faster targeted edits'). There's zero waste or redundancy, making it easy to parse quickly.

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 0 parameters, 100% schema coverage, and an output schema exists, the description doesn't need to explain return values or parameters. However, as a list tool with no annotations, it lacks context on permissions, result format, or how 'grouped' is defined, which could help an agent use it correctly. It's minimally adequate but has gaps in behavioral transparency.

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 documentation is needed. The description doesn't need to compensate for any gaps, and it appropriately doesn't discuss parameters. A baseline of 4 is applied since no parameters exist, and the description doesn't add unnecessary param info.

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 ('grouped develop parameter sets'), and mentions the benefit ('for faster targeted edits'). It distinguishes from siblings like 'list_develop_parameters' by focusing on groups rather than individual parameters. However, it doesn't explicitly contrast with 'get_develop_group_settings' which might retrieve settings for a specific group.

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 like 'list_develop_parameters' or 'get_develop_group_settings'. It mentions 'faster targeted edits' as a benefit, but doesn't specify prerequisites, exclusions, or typical workflows where this tool is preferred over others.

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