apple-photos-mcp

Overview Schema Source Related Servers Discussions Admin

get-photos

Batch fetch full metadata for multiple photo UUIDs in one request, including EXIF, score, detected text, and shared-album details.

Instructions

Use when: you have SEVERAL UUIDs (typically from query or find-duplicates) and want full metadata for all of them — a dedupe review, an EXIF audit, a captioning pass. One batched sidecar round-trip (max 50 UUIDs) instead of N get-photo calls. Returns: count, photos (full per-photo detail — the same shape as get-photo, including the exif block, score, detectedText, and shared-album owner/comments/likes), and notFound listing any requested UUIDs that matched nothing. Do not use when: you have a single UUID — use get-photo; you don't have UUIDs yet — use query; or you want to see the images — use get-thumbnail per photo.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`uuid`	Yes	Photo UUIDs (1–50, as returned by query)
`library`	No	Path to a .photoslibrary (default: system Photos library)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`photos`	No
`notFound`	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
```
Addedv1.5.0Jul 10, 2026

TDQS

A4.5/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 transparency burden. It discloses the batch cap, the single sidecar round-trip vs N calls, the return shape including notFound for unmatched UUIDs, and the included metadata blocks. It does not explicitly state read-only/non-mutating behavior, but the 'get' verb and output description make that reasonably clear.

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?

The description is well-structured and front-loaded: it opens with the use case, then summarizes the return value, then lists exclusions. Every sentence carries routing or behavioral information, and there is no filler or tautology.

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?

For a two-parameter batched getter, the description is self-sufficient: it explains when to use it, what is returned, how missing UUIDs are surfaced via notFound, and which sibling tools to use instead. The output schema covers detailed field structure, so nothing essential is missing.

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 helpful source context ('typically from query or find-duplicates') and reinforces the 50-UUID cap, but it does not add substantial meaning beyond the schema's uuid and library descriptions.

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 states a precise purpose: retrieve full metadata for multiple photo UUIDs in one batched call, with the same per-photo shape as get-photo. It also names the typical input sources (query or find-duplicates), making the tool's role clear and distinct from siblings like get-photo and get-thumbnail.

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 description gives explicit 'Use when' conditions (several UUIDs for dedupe review, EXIF audit, captioning pass) and explicit 'Do not use when' conditions with named alternatives: get-photo for a single UUID, query when no UUIDs exist, and get-thumbnail for viewing images. This is model routing guidance, not just a vague hint.

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