Skip to main content
Glama

add_to_collection

Add selected photos to a Lightroom Classic collection for organized catalog management and workflow automation.

Instructions

Add selected photos (or specific local_ids) to a collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'add_to_collection' tool, which uses the MCP decorator and calls the underlying Lightroom catalog service.
    @mcp.tool()
    async def add_to_collection(
        collection_id: int,
        local_ids: list[int] | None = None,
    ) -> dict[str, Any]:
        """Add selected photos (or specific local_ids) to a collection."""
        ids = validate_local_ids(local_ids)
        payload: dict[str, Any] = {"collection_id": collection_id}
        if ids:
            payload["local_ids"] = ids
        return await _call("catalog.add_to_collection", payload)
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'selected photos' as an alternative input mode, hinting at UI context dependency, but doesn't disclose permissions needed, whether the operation is reversible, error conditions, or how it interacts with sibling tools like 'remove_from_collection'. More context on mutation effects is needed.

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 and immediately clarifies the two input options. Every word earns its place with no redundancy or fluff, 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 a mutation tool with 2 parameters, 0% schema coverage, no annotations, but an output schema, the description is moderately complete. It covers the basic operation and parameter roles but lacks details on behavioral traits, error handling, and integration with sibling tools. The output schema may mitigate some gaps, but more context is needed for safe use.

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 description must compensate but only partially does. It explains that 'local_ids' can be specific IDs or omitted for 'selected photos', adding meaning beyond the schema's technical definition. However, it doesn't clarify 'collection_id' semantics (e.g., what constitutes a valid ID) or the relationship between the two parameters, leaving gaps.

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 ('Add') and target resources ('selected photos' or 'specific local_ids to a collection'), making the purpose immediately understandable. It distinguishes between two input modes (selected photos vs. specific IDs), though it doesn't explicitly differentiate from sibling 'remove_from_collection' beyond the verb contrast.

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 'create_collection' or 'remove_from_collection'. The description implies usage for adding photos to existing collections but doesn't mention prerequisites (e.g., needing a collection_id) or exclusions (e.g., what happens if photos are already in the collection).

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