Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb

find-duplicates

Locate groups of exact duplicate photos in your library, with per-member details like filename, date, and size for cleanup or audit.

Instructions

Use when: you want to find exact duplicates across the library — cleaning up after a double import, checking whether files were re-uploaded, or auditing before a migration/export. Returns: groupCount (total duplicate groups found), returned (groups in this response, capped at limit, default 100), and groups ordered newest-first — each with the member UUIDs plus per-member filename, date, size, dimensions, and movie flag. Use get-thumbnail on members to eyeball a group before acting on it. Do not use when: you're looking for near-duplicates or similar shots — Photos' fingerprint matches EXACT duplicates (identical image data) only; edited copies, resized versions, and burst siblings will NOT group. Safety: read-only. This server cannot delete photos — to act on duplicates, quarantine the extra copies into an album (create-album + add-to-album when writes are enabled, otherwise by hand in Photos.app) and review/delete inside Photos.app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax duplicate groups to return (default 100; groupCount reports the total)
libraryNoPath to a .photoslibrary (default: system Photos library)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupsNo
returnedNo
groupCountNo
Behavior5/5

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

With no annotations, description fully discloses tool is read-only, groups only exact duplicates (not near-duplicates), and explains output structure (groupCount, returned, groups with member details, ordering).

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?

Description is well-structured with clear sections for usage, returns, and safety. Every sentence serves a purpose; no wasted words despite being detailed.

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 straightforward purpose and presence of an output schema, the description covers all essential aspects: use cases, limitations, output details, safety, and integration with other tools (get-thumbnail, create-album).

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?

Input schema has 100% coverage with descriptions for both parameters (limit, library), including defaults and total count note. Description adds no new information about parameter semantics beyond schema.

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 clearly states tool finds exact duplicates across the library, lists specific use cases (cleanup, re-upload check, audit), and distinguishes it from siblings that handle near-duplicates or other operations.

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 'Use when:' and 'Do not use when:' sections provide clear guidance on appropriate scenarios and limitations. Also recommends follow-up actions like using get-thumbnail and creating albums.

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