Skip to main content
Glama

export_photo

Exports one photo from the macOS Photos library to an allowed folder as a still image, saving the edited version when available without launching Photos or overwriting files.

Instructions

Write one photo out as a still image file (Full Disk Access).

Writes the edited still, the image as Photos shows it; the original when there is no edit. id is a photo id from photos (the old <UUID>/L0/001 form is accepted). dest_dir must be inside the allowed root (~/Downloads by default; MACOS_APPS_FILE_ROOT moves it) and is created if needed; a path outside it is REFUSED. The filename is derived from the original name plus the first 8 characters of the id, and an existing file is never overwritten. Files over 250 MiB are refused.

Reads the library at rest, so it never launches Photos and needs no Automation. A photo whose file is only in iCloud comes back status: "absent" with a reason: nothing is downloaded. Videos are refused; a Live Photo exports its still only and says skipped: "live photo motion". Hidden and Recently Deleted ids are refused.

Returns {id, status: "written", path, bytes, edited, dest_dir}. Additive: writes a new file, never modifies the Photos library.

Input Schema

NameRequiredDescriptionDefault
idYes
dest_dirYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.15.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnly=false/destructive=false; the description adds substantial context beyond that: Full Disk Access requirement, no Photos launch or Automation needed, no overwrites, 250 MiB cap, path-root enforcement, and status values for refusal cases. This is exactly the extra behavioral detail the annotations cannot convey.

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?

Front-loaded with the action, then parameters/constraints, then return shape — a logical progression with no filler sentences. It is on the long side, but each constraint (iCloud, videos, Live Photos, hidden) maps to a distinct failure mode an agent must anticipate.

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?

Despite an output schema existing, the description also states the return shape ({id, status, path, bytes, edited, dest_dir}) plus the non-written statuses, and covers permissions, filesystem limits, and library-state edge cases. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does: `id` is a Photos photo id with the legacy `<UUID>/L0/001` form accepted, and `dest_dir` must be inside an allowed root (~/Downloads default, MACOS_APPS_FILE_ROOT override), is auto-created, and is REFUSED if outside. Every parameter gets meaning, defaults, and failure semantics.

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?

Opens with a specific verb+resource: 'Write one photo out as a still image file'. It also clarifies the edited-vs-original semantic, which no sibling (photos, photo_info) handles, so an agent can distinguish export from listing/inspection without opening schemas.

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

Usage Guidelines4/5

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

Rich conditional routing: videos refused, Live Photos export still only, hidden/Recently Deleted refused, iCloud-only photos return 'absent'. It does not explicitly name a sibling alternative (e.g. use photo_info first to verify), but the refusal conditions effectively define when this tool won't work.

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