Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb

export

Copy selected photos from the Apple Photos library to a destination folder, with options for edited, live, or raw versions. Existing files are skipped unless overwrite is enabled.

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: the only side-effecting tool on the read path — it writes files into the destination directory (created if missing); the opt-in write tools (APPLE_PHOTOS_MCP_ENABLE_WRITES=1) can also modify the library, but nothing else here writes anywhere. 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?

With no annotations, the description carries full burden and delivers richly: it warns this is the only side-effecting tool on the read path, explains overwrite behavior (overwrites vs skips), path restrictions, and the iCloud AppleScript fallback requiring Photos.app and Automation permission. This goes far beyond minimal expectations.

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?

Though lengthy, every sentence earns its place. The description is logically structured (use when, returns, do not use when, safety) and front-loads the primary purpose. It packs high-density information without fluff, making the length justified for a tool with this complexity.

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?

The description covers all essential operational aspects: return values, skip reasons, file overwrite behavior, path security constraints, iCloud fallback, performance considerations (slow for large batches), and prerequisites. With an output schema present, no further return-value detail is needed. The context is complete for an agent to invoke and trust the tool.

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 nuance beyond schema: 'edited=true for the edited version', 'live=true to also include', 'raw=true to also include', and the default skip/overwrite behavior for existing files. It does not elaborate on 'library', but the schema already sufficiently describes it. Overall, the extra semantics push it above baseline.

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 explicitly states the tool copies photos (by UUID) to a destination directory on disk, which is a specific verb+resource+destination. It distinguishes itself from siblings by contrasting with get-photo (metadata/paths only) and query (finding photos), 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 'Use when' and 'Do not use when' sections explicitly give usage context and alternatives: use for copying files, avoid for metadata-only needs (use get-photo) or when still identifying photos (use query). This is exactly the kind of clear decision guidance missing in many tool descriptions.

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