Skip to main content
Glama
baramesh

Lightroom MCP Elite

by baramesh

lightroom_set_rating

Rate selected photos from zero to five stars, applying a consistent rating across multiple images to organize your Lightroom catalog.

Instructions

Set star rating (0 to 5) on one or more photos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ratingYes
photo_idsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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, the description carries the full burden of behavioral disclosure. It usefully states the valid rating range (0 to 5) and that multiple photos can be affected, but it does not mention whether existing ratings are overwritten, whether rating 0 clears a rating, or any side effects or permissions.

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?

A single concise sentence with all core information front-loaded. No filler or redundant phrasing.

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?

For a simple two-parameter tool, the description covers the essential operation but lacks when-to-use guidance, overwrite semantics, and behavioral side-effect disclosure. The presence of an output schema covers return values, but operational context is still incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description compensates by explaining the rating scale and the multi-photo capability of photo_ids. It does not elaborate on mixed string/integer IDs, but the schema already communicates the accepted types.

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 'Set star rating (0 to 5) on one or more photos' clearly identifies the action, the target resource, and the scope. However, it does not distinguish itself from the sibling tool 'set_rating', which appears to be an alternative for the same operation.

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 about when to use this tool versus the sibling 'set_rating' or other setter tools. The description only states what the tool does, leaving an agent without criteria for choosing between similarly named tools.

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