Create a new collection in the active Lightroom catalog, optionally nested under a parent set, to organize photos for editing, search, and export workflows.
Create a new collection in the active catalog.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| parent_set_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does 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 only states the creation action and offers no information about side effects, duplicate name handling, permissions, or whether the parent_set_id changes behavior meaningfully.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler or redundancy. Every word contributes to the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter create operation with an output schema, the description is minimally viable: an agent can infer the basic call. However, it lacks parameter semantics, usage routing, and behavioral context, leaving notable gaps for an agent trying to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description provides no additional meaning for either parameter. 'parent_set_id' remains unexplained beyond its title, and the description does not clarify the default behavior when it is omitted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Create') and the resource ('a new collection'), with scope ('in the active catalog'). It is easy to tell this is about creating collections rather than presets or photo exports, though it doesn't explicitly contrast it with close siblings like add_to_collection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool versus alternatives such as add_to_collection or lightroom_create_collection. The 'active catalog' context is helpful, but there are no exclusions, prerequisites, or routing hints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.