Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb

export

Copy photos from Apple Photos to a disk directory. Supports original, edited, live photo, and 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. Returns: the destination path, counts of files exported and skipped, the exported file paths, and a per-UUID reason for anything skipped (e.g. edited=true requested but no edits exist). 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). With overwrite=true it OVERWRITES existing files of the same name in place; without it, existing files are skipped. 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)
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 fully covers behavioral traits: writes files, creates dest dir, overwrite behavior, iCloud fallback via AppleScript (slow, requires permissions), and skip reasons. It also warns this is the only side-effecting tool.

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?

Well-organized into clear sections: Use when, Returns, Do not use, Safety. Each sentence serves a purpose; no redundancy or vague phrasing.

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 no annotations and 7 parameters, the description covers all key aspects: purpose, usage, safety, return values, edge cases (iCloud, overwrite, skip reasons). Output schema exists but description still explains return structure. Highly complete.

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?

Input schema has 100% coverage, but description adds value by explaining default export (original) and how boolean flags combine (edited, live, raw). Also clarifies overwrite effect and dest creation. Baseline 3, plus extra context raises to 4.

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 (by UUID) to a destination directory, with options for edited, live, raw versions. It distinguishes from siblings like get-photo (metadata) and query (finding photos).

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 states 'Use when' to copy photos to disk, and 'Do not use when' for metadata (use get-photo) or deciding which photos (use query). Provides clear alternatives and context.

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