Skip to main content
Glama

get_selected_photo_files

Retrieve file details for photos selected in Lightroom Classic to inspect metadata and properties for editing workflows.

Instructions

List selected Lightroom photos with direct file-inspection details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `get_selected_photo_files` function is implemented here as an MCP tool. It retrieves selected photos and enhances them with file-inspection details using `_normalize_photo_for_inspection`.
    async def get_selected_photo_files(limit: int = 200) -> dict[str, Any]:
        """List selected Lightroom photos with direct file-inspection details."""
        response = await get_selected_photos(limit=limit)
        photos = response.get("photos")
        if not isinstance(photos, list):
            return {
                **response,
                "photos": [],
            }
        return {
            **response,
            "photos": [
                _normalize_photo_for_inspection(photo)
                for photo in photos
                if isinstance(photo, dict)
            ],
        }
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 'direct file-inspection details' but doesn't disclose behavioral traits such as permissions needed, rate limits, whether it's read-only or mutative, or what the output format entails. This leaves significant gaps for a tool that likely interacts with photo files.

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 that front-loads the core purpose without unnecessary words. It directly communicates the action and key detail, making it highly concise and well-structured.

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 no annotations, 0% schema description coverage, but an output schema exists, the description is minimally adequate. It states what the tool does but lacks behavioral context, parameter explanations, and usage guidelines. The output schema may cover return values, but the description doesn't fully compensate for other gaps in a tool that likely handles photo data.

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%, with one parameter ('limit') documented only in the schema. The description adds no parameter semantics, failing to explain what 'limit' controls or how it affects the listing. Since there's only one parameter, the baseline is 4, but the lack of any parameter context in the description reduces it to 3.

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 verb ('List') and resource ('selected Lightroom photos'), specifying the scope as 'selected' photos with 'direct file-inspection details'. It distinguishes from siblings like 'get_selected_photos' by emphasizing file-level details, though it doesn't explicitly name that sibling for full differentiation.

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 like 'get_selected_photos' or 'get_active_photo_file'. The description implies usage for file-inspection details but doesn't specify prerequisites, exclusions, or contextual triggers for selection.

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