Read-only access to the macOS Photos library. Search photos, list albums, view metadata, and retrieve image thumbnails or full-size images.
PhotosMCP demonstrates solid definition quality with consistently named tools following verb_noun patterns (list_albums, get_library_stats, search_photos, etc.). All 12 tools have clear, descriptive names and documented purposes. Input schemas are present and properly typed with JSON Schema. Descriptions are well-crafted (averaging ~120 chars, within the 10-1024 char baseline for good tool descriptions). However, there are notable gaps: (1) Output schemas are not formally documented in the source, we infer structure from helper functions like PhotoKitHelpers.encodeToJSON() but cannot see the actual response shape contracts; (2) Several parameters lack explicit range constraints in descriptions (e.g., max_dimension, radius_km, limit default to reasonable values but min/max bounds are not always stated); (3) Error messages are functional but could be more actionable (e.g., 'Asset not found' lacks recovery guidance like 'Check the asset_identifier or call list_albums first'); (4) No explicit permission/scope declarations visible; (5) Security considerations around sensitive metadata (location, EXIF) are not discussed in tool descriptions. Strengths: all tools are read-only (READ_ONLY risk marks), well-scoped to single concerns (e.g., get_asset_details vs get_asset_classifications vs get_asset_classifications are cleanly separated), accept pagination parameters consistently, and use human-friendly identifiers (album_identifier, asset_identifier are opaque but expected in a Photos framework context).
Return asset metadata for all items in a given album by album identifier.
Return Vision image classification labels and confidence scores for a photo. Useful when keyword search misses an expected object.
Return full metadata for an asset: EXIF, dates, GPS, dimensions, media subtypes, duration (video), resource sizes.
Return total counts of photos, videos, albums, and date range of the library.
Full-resolution image (use this when user wants full size, not thumbnails). Saves to temp file; tell user `open /path` to view. Use max_dimension (e.g. 2048) to limit size.
Small preview (default 512px). For full resolution use get_photo_full. Saves to temp file; tell user `open /path` to view.
Output schemas not formally documented. Response structure inferred from helper functions (PhotoKitHelpers.encodeToJSON, SearchResponse, AssetMetadataWithSizes, AssetClassificationsResponse) but not exposed as JSON Schema definitions. LLMs cannot plan downstream actions without knowing what fields to extract.
Pagination parameters (limit, offset) present but lack explicit constraints in descriptions. Code enforces max=200 and defaults (e.g., limit defaults to 50) but descriptions do not state these bounds. LLMs may pass invalid values that violate the constraint.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 60 | <=2025-11-25 | v2 |
Find photos taken on a specific date or within a date range.
Find photos within a radius (km) of given latitude and longitude coordinates.
Find photos by place name (city, country). Geocodes the name and finds photos taken nearby. Use for 'photos from Valencia', 'pictures in Paris', etc.
Return all user albums and smart albums with name, identifier, asset count, and type.
Return photo moments/collections grouped by time and location.
Search the Photos library by date range, media type, favorite status, or keyword.
Error messages lack recovery guidance. Examples: 'Error: album_identifier is required', 'Error: Asset not found with identifier <id>'. No suggestions for next steps (e.g., 'Try list_albums() to find valid album identifiers' or 'Call search_photos() with a date range to locate assets').
No explicit permission or scope declarations. Tools access sensitive data (GPS location, EXIF, creation dates, favorite status, hidden photos). Tool descriptions should declare required permissions (e.g., 'Requires Photos.read permission') for audit and least-privilege configuration.
keyword parameter in search_photos uses Vision ML but offers no guidance on performance/cost or when to combine with date ranges. Description mentions 'Combine with date range for large libraries' but does not explain why or what happens without it.