Skip to main content
Glama
Sign In
Lightroom Classic MCP Server

Lightroom Classic MCP Server

by yopiesuryadi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

start_import

Queue files or folders for import into Lightroom Classic, optionally adding to a collection or moving to a destination folder.

Instructions

Queue a Lightroom Classic import job and return immediately with a job_id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paths": "<paths>"
    },
    "name": "start_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesFiles or folders to import into Lightroom Classic.
move_toNoOptional destination folder for Lightroom's import move/copy flow.
collectionNoOptional collection name to add imported photos to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations provided, so the description must convey behavioral traits. It mentions the async queue behavior and immediate return of job_id, but omits details like error handling, permission requirements, or potential side effects.

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, concise sentence that efficiently conveys the core functionality without extraneous words.

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?

With 3 parameters, no output schema, and no annotations, the description is minimally adequate. It explains the immediate return of job_id but doesn't clarify how to use it (e.g., polling with job_status), which limits completeness for an agent.

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 has 100% coverage with descriptions for all three parameters. The tool description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Queue'), the resource ('Lightroom Classic import job'), and the async nature ('return immediately with a job_id'). It distinguishes from siblings like start_export and cancel_job.

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 on when to use this tool versus alternatives such as start_export, or any prerequisites. The description lacks context for selecting this tool over sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools