Skip to main content
Glama

send_raw_lightroom_command

Send custom commands to Adobe Lightroom Classic for advanced automation, debugging, and direct plugin control.

Instructions

Send a raw command to the plugin (advanced/debug use).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function implementation for the tool 'send_raw_lightroom_command', which calls the internal '_call' method to forward commands to the Lightroom bridge.
    async def send_raw_lightroom_command(command: str, params: dict[str, Any] | None = None) -> dict[str, Any]:
        """Send a raw command to the plugin (advanced/debug use)."""
        if not command:
            raise ValueError("command is required")
        return await _call(command, params or {})
  • The @mcp.tool decorator registers 'send_raw_lightroom_command' as a tool for the MCP server.
    @mcp.tool()
    async def send_raw_lightroom_command(command: str, params: dict[str, Any] | None = None) -> dict[str, Any]:
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. It mentions 'advanced/debug use,' hinting at potential risks or complexity, but fails to disclose critical behavioral traits like required permissions, side effects (e.g., if it modifies data), rate limits, or error handling. This leaves significant gaps for safe and effective use.

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 zero waste, front-loaded with the core action and context. It's appropriately sized for a simple tool, though brevity contributes to gaps in other dimensions.

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?

Given complexity (advanced/debug tool with 2 parameters), no annotations, 0% schema coverage, but an output schema exists, the description is incomplete. It lacks details on behavior, parameters, and usage scenarios, making it inadequate for safe invocation despite the output schema covering return values.

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%, so the schema provides no parameter details. The description adds no meaning beyond the schema, not explaining what 'command' or 'params' represent, their formats, or examples. With 2 parameters and low coverage, the description fails to compensate, leaving parameters undocumented.

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

Purpose3/5

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

The description states the tool 'Send[s] a raw command to the plugin' which clarifies the action (send) and target (plugin), but it's vague about what 'raw command' entails or what plugin it refers to. It distinguishes from siblings by being for 'advanced/debug use,' but lacks specificity on the resource or exact function compared to other tools like 'lightroom_list_commands' or 'lightroom_ping.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states this is for 'advanced/debug use,' providing clear context on when to use it (for debugging or advanced operations) and implying it's not for routine tasks. However, it doesn't specify when not to use it or name alternatives among siblings, such as more specific tools like 'apply_develop_settings' for standard operations.

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