Skip to main content
Glama

remove_keywords

Remove specified keywords from selected photos in Lightroom Classic to clean up metadata and organize your catalog more effectively.

Instructions

Remove keywords by name/path from selected photos or local_ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsYes
local_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'remove_keywords' tool handler, which validates input keywords and calls the Lightroom bridge metadata.remove_keywords method.
    async def remove_keywords(keywords: list[str], local_ids: list[int] | None = None) -> dict[str, Any]:
        """Remove keywords by name/path from selected photos or local_ids."""
        if not keywords:
            raise ValueError("keywords cannot be empty")
        payload: dict[str, Any] = {"keywords": [str(k) for k in keywords]}
        ids = validate_local_ids(local_ids)
        if ids:
            payload["local_ids"] = ids
        return await _call("metadata.remove_keywords", payload)
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It states the action is a removal but doesn't disclose if this is destructive, reversible (e.g., via 'undo'), requires specific permissions, or has side effects. The phrase 'from selected photos or local_ids' hints at scope but lacks detail on behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it easy to parse. However, it could be more front-loaded with critical details like tool context or behavioral traits.

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 no annotations, 0% schema coverage, and a mutation tool with potential side effects, the description is incomplete. It lacks behavioral context, parameter explanations, and usage guidance. While an output schema exists, the description doesn't address core aspects like what 'selected photos' means or how removal affects the system.

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 description must compensate but adds little. It mentions 'keywords' and 'local_ids' by name but doesn't explain what 'keywords' are (e.g., tags, metadata), what 'local_ids' refer to, or the relationship between parameters. The description fails to clarify semantics beyond the schema's structure.

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 ('Remove') and target ('keywords') with scope ('from selected photos or local_ids'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling 'add_keywords' beyond the obvious verb difference, nor does it specify what 'selected photos' means in context.

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. While 'add_keywords' is a clear sibling, the description doesn't mention it or explain prerequisites like how photos become 'selected'. Usage context is implied but not stated.

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