Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb

remove-from-album

Removes specified photos from an album, undoing misfiling or clearing reviewed items. Does not delete photos from the library.

Instructions

Use when: you want to take photos OUT of an album — undoing a mis-filing, or clearing reviewed items from a quarantine album. This removes ALBUM MEMBERSHIP only. Returns: the album AFTER the operation ({uuid, name, path} — note the uuid CHANGES when anything was removed), removedCount, removed, notInAlbum (requested UUIDs that weren't members — no-ops), albumRecreated, and previousAlbumUuid. Do not use when: you want to delete photos from the library — this server cannot delete photos at all (quarantine them in an album and review in Photos.app instead); or the photos aren't in the album (harmless, but pointless). Safety: WRITE tool — disabled unless APPLE_PHOTOS_MCP_ENABLE_WRITES=1 (run doctor to check). NEVER deletes photos from the library — removed photos stay in All Photos and every other album. Photos' AppleScript has no remove-from-album verb, so the album is REBUILT (same name and remaining photos): its UUID changes and any custom manual sort order is lost; re-fetch the album UUID from the response. When none of the UUIDs are members, nothing is rebuilt. Max 100 UUIDs per call. Drives Photos.app via AppleScript (requires macOS Automation permission). Writes target the library currently open in Photos.app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesPhoto UUID(s) to remove from the album (1–100)
albumYesAlbum name or UUID (UUID-looking values try the id lookup first)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
albumNo
removedNo
notInAlbumNo
removedCountNo
albumRecreatedNo
previousAlbumUuidNo
Behavior5/5

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

Comprehensively documents side effects: album rebuild, UUID change, sort order loss, max 100 UUIDs, macOS Automation requirement, env var toggle, no photo deletion. No annotations provided, so description carries full burden and excels.

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?

Well-organized with clear sections (use when, returns, do not use, safety, details). Every sentence provides necessary information without redundancy. Front-loaded with purpose and usage.

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?

Covers all aspects: return values, edge cases (notInAlbum, no-op on non-members), side effects (UUID change, sort order loss), constraints (max 100), prerequisites (env var, macOS permission), and rationale (no AppleScript verb). Complete for a write tool with no annotations.

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?

Input schema has 100% coverage, baseline 3. Description adds value by clarifying album parameter format (name or UUID with id lookup priority) and behavioral context of uuid array. Exceeds schema alone.

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?

Clearly states the tool removes photo membership from albums, distinguishing from deletion. Explicitly positions as opposite of adding to album, though lacks direct sibling comparison but sufficiently clear.

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 with concrete scenarios (mis-filing, quarantine, album membership only). Provides alternative for deletion and notes pointless usage. Includes safety prerequisites.

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