apple-photos-mcp

Overview Schema Source Related Servers Discussions Admin

add-to-album

Add photo UUIDs to an existing album, idempotently filing them for organization. Returns newly added and already-present IDs, and only modifies album membership.

Instructions

Use when: you have photo UUIDs (from query / find-duplicates) and want to file them into an album — e.g. collecting duplicate extras into a quarantine album, or filing a trip's photos. Returns: the album {uuid, name, path}, addedCount, added (UUIDs newly added), alreadyPresent (UUIDs that were already members — adding is idempotent), and notFound (requested UUIDs that don't exist in the library). Fails only when the album doesn't exist or NO requested photo exists. Do not use when: the album doesn't exist yet — call create-album first; or you want photos OUT of an album — use remove-from-album. Safety: WRITE tool — disabled unless APPLE_PHOTOS_MCP_ENABLE_WRITES=1 (run doctor to check). Changes album membership only: photos are never copied, modified, or deleted, and each target is validated to exist first. Max 100 UUIDs per call. Drives Photos.app via AppleScript (launches it if needed; requires macOS Automation permission — one-time prompt). Writes target the library currently open in Photos.app.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uuid`	Yes	Photo UUID(s) to add (1–100, as returned by query)
`album`	Yes	Album name or UUID (UUID-looking values try the id lookup first)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`added`	No
`album`	No
`notFound`	No
`addedCount`	No
`alreadyPresent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.13Sep 24, 2026

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"

Changed1 schema field changedv2.1.9Aug 7, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
Addedv2.0.0Jul 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

No annotations exist, so the description carries the full burden — and it delivers thoroughly. It discloses write semantics with an environment-var gate, idempotency, non-destructiveness (photos never copied/modified/deleted), the 100-UUID cap, AppleScript driving, Photos.app launching, and the Automation permission requirement.

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 long but uses labeled, front-loaded sections ('Use when', 'Returns', 'Do not use when', 'Safety') that make scanning easy. Every sentence carries information; the length is justified by the complexity of a write tool with environment gating, permissions, and return semantics.

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 zero annotations, the description is remarkably complete: it covers return shape, failure modes, prerequisites, environmental gating, side effects (launching Photos.app), permission requirements, and the library-targeting caveat. No critical information an agent needs to call it correctly is missing.

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 coverage is 100%, so baseline is 3. The description adds meaningful value beyond the schema: it explains the album parameter's lookup behavior ('UUID-looking values try the id lookup first'), maps return fields (addedCount, alreadyPresent, notFound) back to parameter outcomes, and clarifies failure conditions tied to the inputs.

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 states a specific verb and resource ('file photo UUIDs into an album') with concrete example use cases, and differentiates from siblings by naming create-album and remove-from-album. An agent can immediately tell what this tool does and what it does not do.

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?

Explicit 'Use when' and 'Do not use when' sections give direct conditions and name the alternative tools (create-album for missing albums, remove-from-album for removing photos). The prerequisite about album existence is stated explicitly.

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