Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb

set-photo-date

Correct wrong dates in Apple Photos by setting a new date or shifting by seconds. Use dry-run to preview, then apply to write the change.

Instructions

Use when: a photo's date/time is wrong and you want to fix it — trailcam or scanner imports stamped with the upload time, a camera with a mis-set clock, scanned prints. Set an absolute date OR shift by a number of seconds (exactly one of date / shiftSeconds). DRY RUN BY DEFAULT: with dryRun omitted (or true) it only reports the current and would-be dates — preview first, then re-run with dryRun=false to write. Returns: uuid, before and after datetimes (on a dry run, after = the would-be date), shiftSeconds (the effective delta), applied, and dryRun. Revert an applied change by re-running with date= and dryRun=false. Do not use when: you want to find photos by date — use query; or you expect the file's EXIF to change — this edits the Photos library date only. Safety: WRITE tool — disabled unless APPLE_PHOTOS_MCP_ENABLE_WRITES=1 (run doctor to check). Rewrites the photo's date in the Photos LIBRARY DATABASE only — the same operation as Photos.app's 'Adjust Date & Time'; the original file's EXIF is never modified. Dates are interpreted in the Mac's local timezone (a timezone-aware ISO datetime is converted to local). Nothing is written unless dryRun=false is passed explicitly, and before/after are always echoed so any change can be reverted. The target photo is validated to exist first. Drives Photos.app via AppleScript (requires macOS Automation permission). Writes target the library currently open in Photos.app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoAbsolute new date-time, ISO 8601 (e.g. 2026-05-14T06:32:00), interpreted in the Mac's local timezone unless a UTC offset is included. Exactly one of date / shiftSeconds
uuidYesPhoto UUID (hex-with-dashes, as returned by query)
dryRunNoDefault TRUE: preview the before/after dates without writing anything. Pass false to actually write the new date
shiftSecondsNoShift the current date by this many seconds (negative = earlier; e.g. -86400 = one day back). Exactly one of date / shiftSeconds

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidNo
afterNo
beforeNo
dryRunNo
appliedNo
shiftSecondsNo
Behavior5/5

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

With no annotations, the description fully discloses behavior: dry-run default, write operation, safety guardrails, timezone handling, EXIF untouched, validation, AppleScript permissions, and library targeting. It even explains the revert mechanism, giving complete transparency.

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 well-organized with clear sections (Use when, Do not use when, Safety, Returns) and front-loaded with the core action. It avoids redundancy and is appropriately detailed for a write tool with safety implications.

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 (write operation, dry-run, timezone, safety), the description is exceptionally complete. It covers prerequisites, side effects, return values, revert strategy, and exclusions, all without relying on annotations or an output schema. It answers virtually any question an agent might have.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description adds minimal extra parameter meaning beyond the schema, only reiterating the mutual exclusivity of date/shiftSeconds and the dryRun default. It includes practical usage context like preview-first, but that's more usage guidance than parameter 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?

The description explicitly states the tool's function: fixing a photo's date/time by setting an absolute date or shifting by seconds. It clearly distinguishes from sibling tools by saying 'Do not use when: you want to find photos by date — use query' and notes it only edits the Photos library date, not EXIF.

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?

Provides detailed 'Use when' scenarios (trailcam/scanner imports, mis-set clock, scanned prints) and explicit 'Do not use when' exclusions with alternatives (e.g., query for finding photos by date). Also explains the dry-run-first workflow and safety prerequisites like APPLE_PHOTOS_MCP_ENABLE_WRITES=1.

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