Skip to main content
Glama

rotate_left

Rotate selected photos 90 degrees counterclockwise in Adobe Lightroom Classic to correct orientation or adjust composition.

Instructions

Rotate selected photos 90 degrees left.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'rotate_left' tool. It includes the @mcp.tool() registration decorator and the logic that calls the underlying 'metadata.rotate_left' bridge function.
    @mcp.tool()
    async def rotate_left(local_ids: list[int] | None = None) -> dict[str, Any]:
        """Rotate selected photos 90 degrees left."""
        ids = validate_local_ids(local_ids)
        payload: dict[str, Any] = {}
        if ids:
            payload["local_ids"] = ids
        return await _call("metadata.rotate_left", payload)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but doesn't disclose behavioral traits like whether this is destructive (modifies original files), requires specific permissions, has rate limits, or provides confirmation/undo capabilities. The description is minimal and lacks operational context needed for safe invocation.

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 wasted words. It's front-loaded with the core action and includes all essential elements (action, target, direction). Every word earns its place, making it easy to parse quickly.

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 handles return values) and moderate complexity (single parameter mutation), the description is minimally complete but lacks important context. Without annotations, it should disclose more about the mutation's nature (destructive vs. reversible), permissions, or side effects. The description covers the basic what but not the how or implications.

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 description coverage is 0%, so the description must compensate. It mentions 'selected photos' which relates to the 'local_ids' parameter, adding meaning about what the parameter controls. However, it doesn't explain parameter format, optionality, or what happens when null/default is used. The description provides basic context but doesn't fully compensate for the schema gap.

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 ('rotate') and target ('selected photos') with specific direction ('90 degrees left'). It distinguishes from sibling 'rotate_right' by specifying left rotation. However, it doesn't explicitly differentiate from other photo manipulation tools like 'reset_current_photo' or 'auto_tone' beyond the rotation action.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing photos selected), exclusions, or comparisons to similar tools like 'rotate_right' or other editing operations. It simply states what the tool does without contextual usage information.

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