Skip to main content
Glama

remove_from_collection

Remove selected photos from a Lightroom Classic collection to organize your catalog by deleting unwanted images from specific sets.

Instructions

Remove selected photos (or specific local_ids) from a collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the `remove_from_collection` MCP tool, which validates IDs and calls the internal `catalog.remove_from_collection` command.
    @mcp.tool()
    async def remove_from_collection(
        collection_id: int,
        local_ids: list[int] | None = None,
    ) -> dict[str, Any]:
        """Remove selected photos (or specific local_ids) from 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.remove_from_collection", payload)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool removes photos from a collection, implying a destructive mutation, but doesn't clarify whether this action is reversible (e.g., via 'undo'), what permissions are required, or how errors are handled (e.g., if local_ids don't exist). The description lacks critical behavioral context for a mutation tool.

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 with no wasted words. It front-loads the core action ('Remove') and specifies the target clearly. Every part of the sentence contributes directly to understanding the tool's function.

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 has an output schema (which reduces the need to describe return values) but no annotations and 0% schema coverage, the description is moderately complete. It covers the basic purpose but lacks details on parameters, behavioral traits, and usage context. For a mutation tool with two parameters, this leaves significant gaps in understanding.

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

Parameters2/5

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

Schema description coverage is 0%, meaning parameters are undocumented in the schema. The description mentions 'collection_id' and 'local_ids' implicitly but doesn't explain their semantics—for example, what a 'local_id' represents, whether 'local_ids' can be empty, or how the tool behaves if 'local_ids' is null. It adds minimal value beyond the parameter names visible in the schema.

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 ('Remove') and target ('selected photos (or specific local_ids) from a collection'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'add_to_collection' by specifying removal rather than addition. However, it doesn't explicitly mention what type of collection or system this operates on, which prevents a perfect score.

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., needing an existing collection), exclusions, or related tools like 'delete_collection' (which might delete the entire collection rather than remove items from it). The agent must infer usage from context alone.

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