Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb

get-thumbnail

Preview a photo as an inline image to inspect details, pick the best shot, or read text, without exporting the file.

Instructions

Use when: you (or the user) want to SEE a photo — visual triage ('show me…'), picking the best shot, eyeballing duplicate groups, or reading text in an image — without exporting anything to disk. Prefer this over export whenever the goal is to LOOK at a photo rather than to obtain the file. Returns: the photo as an inline MCP image content block (base64 JPEG/PNG a vision-capable client renders directly), plus a text summary and structured metadata (source path, width/height, MIME type, byte size, isDerivative). It serves the smallest Photos-generated preview derivative whose long edge is at least minSize pixels (default 360) — raise minSize (e.g. 1024) when you need detail like small text; isDerivative=false means no suitable derivative existed and the original was downscaled/converted via sips. Do not use when: you need the full-resolution file on disk — use export; or you only need metadata — use get-photo. Movies get a thumbnail only when Photos generated a poster-frame derivative; an iCloud-only photo with no local derivative or original cannot be thumbnailed (export it first, which downloads on demand).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesPhoto UUID (hex-with-dashes, as returned by query)
libraryNoPath to a .photoslibrary (default: system Photos library)
minSizeNoSmallest acceptable long-edge size in pixels (default 360). The smallest qualifying derivative is served, so higher values return larger images

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo
uuidNo
widthNo
heightNo
byteSizeNo
mimeTypeNo
isDerivativeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.13
    • 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"
  2. Changed1 schema field changedv2.1.9
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  3. Addedv1.5.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, description carries full burden. It discloses return format (inline MCP image), derivative selection logic, isDerivative flag, downscaling via sips, and limitations (iCloud). All behavioral traits are transparent.

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 'Use when' and 'Returns', then exclusions. Though longer than average, every sentence adds necessary context for a complex tool. No redundancy; well organized.

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?

Comprehensive for the tool's complexity: covers output schema mentions, edge cases, alternatives, and parameter semantics. An agent has all information to select and call correctly.

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?

Schema covers 100% of parameters, but description adds value: explains minSize semantics (smallest qualifying derivative, default 360, raise for detail), and isDerivative interpretation. This goes beyond schema 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?

Description states a specific verb+resource (get thumbnail to SEE a photo) and distinguishes from siblings: 'Prefer this over export' and 'use get-photo' for metadata. It clearly differentiates the tool's role.

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?

Explicit when to use ('want to SEE a photo'), when not to ('need full-resolution file — use export; only metadata — use get-photo'), and edge cases (movies, iCloud-only) are covered. No ambiguity remains.

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