Skip to main content
Glama

create_collection

Organize photos by creating new collections in Lightroom Classic, optionally grouping them within existing collection sets for better catalog management.

Instructions

Create a new collection (optionally inside a collection set).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
parent_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the `create_collection` tool, decorated with @mcp.tool().
    @mcp.tool()
    async def create_collection(name: str, parent_id: int | None = None) -> dict[str, Any]:
        """Create a new collection (optionally inside a collection set)."""
        if not name:
            raise ValueError("name is required")
        payload: dict[str, Any] = {"name": name}
        if parent_id is not None:
            payload["parent_id"] = parent_id
        return await _call("catalog.create_collection", payload)
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 the tool creates something (implying a write/mutation operation) but doesn't mention any behavioral traits like whether it requires authentication, what happens on duplicate names, if changes are reversible, or what the output looks like. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 communicates the core functionality without any wasted words. It's appropriately sized for a simple creation tool and front-loads the essential information ('Create a new collection').

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 there's an output schema (which should document return values), the description doesn't need to explain outputs. However, for a mutation tool with no annotations and 0% schema description coverage, the description is too minimal—it doesn't address behavioral aspects like error conditions, side effects, or usage context. It meets the bare minimum but leaves the agent with significant unknowns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description mentions 'optionally inside a collection set', which hints at the purpose of 'parent_id', but doesn't explain 'name' or provide any details about parameter formats, constraints, or semantics. It adds minimal value beyond what's inferable from parameter names alone.

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 ('Create a new collection') and resource ('collection'), making the purpose immediately understandable. It also mentions the optional parent relationship ('optionally inside a collection set'), which adds useful specificity. However, it doesn't explicitly differentiate from sibling tools like 'list_collections' or 'delete_collection' beyond the obvious verb difference.

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. It doesn't mention prerequisites (e.g., whether you need specific permissions), when not to use it, or how it relates to sibling tools like 'add_to_collection' or 'remove_from_collection'. The agent must infer usage solely from the tool name and parameters.

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