apple-photos-mcp

Overview Schema Source Related Servers Discussions Admin

get-photo

Retrieve complete metadata for a single photo from your Apple Photos library by providing its UUID. Get dimensions, dates, location, albums, keywords, EXIF, and more in one call.

Instructions

Use when: you have a single photo's UUID (typically from query) and want its complete metadata. Returns: dimensions and original dimensions, dates, title/description, location and place, albums, keywords, persons, labels, file paths, size, EXIF camera data (make/model, lens, ISO, aperture, shutter speed, focal length — null when Photos recorded none), Photos' ML intelligence (score = overall aesthetic 0–1, detectedText = OCR-indexed text; null on macOS versions without them), iCloud shared-album social data (owner, comments, likes — only populated for shared assets), and type flags (HDR/live/raw/edited/portrait/panorama/etc.). Pass burstPhotos=true to also list the sibling frames of a burst (UUID, filename, date each). Do not use when: you don't have a UUID yet — use query to find matches first; you have several UUIDs — use get-photos for one batched call; or you want to see the image — use get-thumbnail.

Input Schema

TableJSON Schema

Name	Required	Description
`uuid`	Yes	Photo UUID (hex-with-dashes, as returned by query)
`library`	No	Path to a .photoslibrary (default: system Photos library)
`burstPhotos`	No	true = include burstPhotos: the OTHER frames of this photo's burst set (empty when the photo is not a burst member)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`photo`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.13Sep 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedv2.1.9Aug 7, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

Changed1 schema field changedv2.1.0Jul 10, 2026

addedInput schema / properties / burstPhotos

Added value: +{
+  "description": "true = include burstPhotos: the OTHER frames of this photo's burst set (empty when the photo is not a burst member)",
+  "type": "boolean"
+}

Changed3 schema fields changedv1.4.0Jul 9, 2026
- changedInput schema / properties / uuid / description
```
Previous value: -"Photo UUID"New value: +"Photo UUID (hex-with-dashes, as returned by query)"
```
- addedInput schema / properties / uuid / maxLength
```
Added value: +256
```
- addedInput schema / properties / uuid / pattern
```
Added value: +"^[0-9A-Fa-f-]+$"
```
Changed1 schema field changedv1.1.3Jun 30, 2026
- addedInput schema / properties / library / maxLength
```
Added value: +4096
```

Changed1 schema field changedv1.1.0Jun 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "photo": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.4May 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It thoroughly discloses conditional output behavior: null EXIF fields, macOS version differences, iCloud shared-album data only for shared assets, and burstPhotos semantics. It does not explicitly state read-only/no side effects, but 'get' and 'Returns' make the read-only nature strongly implied.

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 long but well-structured: use-case first, then return content, then exclusions. The metadata enumeration is dense but provides real selection and invocation value. Every section earns its place, though some return-field detail could be trimmed.

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 3 parameters, existing output schema, and lack of annotations, the description is complete: it explains when to use it, what it returns, how optional parameters behave, and which sibling tools to use instead. Nothing significant is missing for an agent to invoke it correctly.

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 the baseline is 3. The description adds useful context about uuid provenance and burstPhotos behavior, but the schema already documents all three parameters accurately. No additional parameter meaning is strictly required.

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?

States a specific verb and resource: getting a single photo's complete metadata by UUID. It explicitly distinguishes itself from get-photos and get-thumbnail, so an agent immediately understands what this tool uniquely does.

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 explicit 'Use when' and 'Do not use when' guidance with named alternatives: query, get-photos, and get-thumbnail. The conditions are concrete, so the agent knows exactly when to choose this tool over its siblings.

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