Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb

export

Copy one or more photos from your Apple Photos library to a destination directory on disk. Supports original, edited, live, or raw versions with optional overwrite.

Instructions

Use when: you want to copy one or more photos (by UUID, typically from query) out to a destination directory on disk. By default exports the original; set edited=true for the edited version, live=true to also include the live-photo video, raw=true to also include the raw image. Large batches report per-photo MCP progress notifications when the request carries a progressToken. Returns: the destination path, counts of files exported and skipped, the exported file paths, and a per-UUID reason for anything skipped (e.g. file already exists at the destination, UUID not found / in trash, iCloud download failed). Do not use when: you only need metadata or file paths rather than copies on disk — use get-photo; or you're still figuring out which photos to export — use query first. Safety: this is the only side-effecting tool — it writes files into the destination directory (created if missing). dest must resolve (after expanding ~ and following symlinks) to a path under your home directory, /tmp, /private/tmp, or /Volumes; anything else is rejected. With overwrite=true it OVERWRITES existing files of the same name in place; without it, existing files are skipped and reported per-UUID. If an original isn't on disk (iCloud 'Optimize Mac Storage'), the export falls back to driving Photos.app via AppleScript to download it on demand — this is slow for large batches and requires Photos.app installed, signed in to iCloud, and Automation permission granted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoAlso export the raw image
destYesDestination directory (created if missing). Must be under the home directory, /tmp, /private/tmp, or /Volumes
liveNoAlso export the live-photo video
uuidYesPhoto UUID(s) to export
editedNoExport the edited version instead of the original
libraryNoPath to a .photoslibrary (default: system Photos library)
overwriteNoOverwrite existing files at the destination

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
skippedNo
exportedNo
destinationNo
skippedCountNo
exportedCountNo
Behavior5/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 discloses side effects (writing files, overwriting), destination restrictions, iCloud download fallback, progress notifications, and return values. This is exceptionally transparent.

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 well-structured with logical sections (when to use, returns, do not use, safety). It is fairly long but every sentence serves a purpose. Could be slightly more compact, but still effective.

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?

Given the tool's complexity (7 parameters, side effects, output schema exists), the description covers usage guidelines, safety constraints, edge cases (iCloud download), and return values comprehensively. Nothing important is omitted.

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%, but the description adds significant context beyond the schema: it explains the effect of each boolean flag (edited, live, raw) and overwrite behavior. Some redundancy with schema descriptions, but overall adds value.

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 clearly states the tool copies photos to a destination directory. It specifies the action ('copy'), the resource ('photos by UUID'), and distinguishes from siblings like get-photo and query.

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?

Explicitly provides 'Use when:' and 'Do not use when:' sections with concrete alternatives (get-photo, query). This clearly guides the agent on when to invoke this tool vs. others.

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/sweetrb/apple-photos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server