Skip to main content
Glama
Sign In
Lightroom Classic MCP Server

Lightroom Classic MCP Server

by yopiesuryadi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

start_export

Queue a Lightroom Classic export job from a specified collection or selection and receive a job ID for tracking.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetNoReserved for future Lightroom export preset support.
collectionNoCollection to export from.
output_dirNoExport destination folder./root/Documents/leica
selected_onlyNoExport current Lightroom selection only.
export_settingsNoOptional advanced Lightroom export settings table override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, description correctly states async behavior (queues, returns immediately with job_id), but does not disclose error conditions, capacity limits, or 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?

Single sentence conveying action, resource, and async behavior; efficient and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks information on how to retrieve export results or monitor progress, despite presence of sibling job-query tools; no output schema means description should hint at return format.

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 covers all parameters with descriptions; description adds no extra semantic value beyond what schema provides.

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 uses specific verb 'queue' and resource 'Lightroom Classic export job', clearly distinguishing from sibling import/edit tools.

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 vs alternatives; lacks context about prerequisites or alternatives like start_edit_tracking.

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