Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

set-photo-metadata

Set a photo's title, description, or favorite flag in Apple Photos. Returns before/after values for easy revert, and validates the photo exists first.

Instructions

Use when: you want to set a photo's title, description, or favorite flag — captioning passes, marking the best shot of a burst, titling scans. Returns: uuid, updated (which fields were written), and the full before/after values of all three fields — so any change can be reverted by writing the before values back. Do not use when: you want keywords — use set-keywords (it has union semantics; this tool doesn't touch keywords); or you only want to READ metadata — use get-photo. Safety: WRITE tool — disabled unless APPLE_PHOTOS_MCP_ENABLE_WRITES=1 (run doctor to check). Metadata only — never touches the image asset, and only the fields you pass are modified (an empty string clears title/description). The target photo is validated to exist first. Drives Photos.app via AppleScript (requires macOS Automation permission). Writes target the library currently open in Photos.app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesPhoto UUID (hex-with-dashes, as returned by query)
titleNoNew title (empty string clears it)
favoriteNoSet or clear the favorite flag
descriptionNoNew description (empty string clears it)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidNo
afterNo
beforeNo
updatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.13
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv2.1.9
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  3. Addedv2.0.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it delivers thoroughly: it declares WRITE semantics, the APPLE_PHOTOS_MCP_ENABLE_WRITES=1 gate, the fact that only passed fields change, empty-string clearing behavior, pre-validation of the photo, AppleScript/Automation permission needs, and the target-library context. It even explains the return payload's revert value.

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 substantial but every sentence earns its place: context, return value, exclusions, safety, side effects, and prerequisites. It is front-loaded with the decision-relevant 'Use when' and 'Do not use when' sections, and the bolding/scanning aids agent parsing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with no annotations, this is complete: it covers return shape, revert mechanism, exclusions to sibling tools, environmental enablement, permissions, side-effect boundaries, and validation behavior. There is no missing operational context an agent would need to invoke it correctly.

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?

The input schema already documents all parameters at 100% coverage, so the baseline is 3. The description adds meaningful behavioral semantics beyond the schema: an empty string clears title/description, only the fields you pass are modified, and favorite is set or cleared. This exceeds the schema baseline without duplicating it.

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

Purpose5/5

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

The description names a specific verb (set), a specific resource (photo metadata), and the exact fields affected: title, description, and favorite flag. It also distinguishes itself from the siblings set-keywords and get-photo in the 'Do not use when' section, making the purpose unmistakable.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool ('Use when'), when not to use it ('Do not use when'), and names the exact alternatives (set-keywords, get-photo) with the reason for choosing them. It also includes environment-enablement and permission prerequisites, leaving no ambiguity about call conditions.

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

Deploy Server

Other Tools