Skip to main content
Glama

export_photos

Copy selected photos to a destination folder, using edited versions when available. Existing files are never overwritten, and photos not downloaded from iCloud are reported as skipped.

Instructions

Copy photos to a folder, using the edited version where one exists.

    Never overwrites existing files. Photos that are not downloaded from iCloud are
    reported as skipped. For more control, use run_osxphotos with the export command.
    

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uuids": "<uuids>",
      "destination": "<destination>"
    },
    "name": "export_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidsYes
destinationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Adds concrete behavior beyond annotations: never overwrites existing files, picks the edited version when present, and reports non-downloaded iCloud photos as skipped. With destructiveHint=false already declared, the no-overwrite guarantee reinforces safety in a meaningful way, though the skip/report format is not detailed.

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?

Three short sentences that are front-loaded and waste nothing: purpose first, then behavioral guarantees, then the alternative. Easy to scan before invoking.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary, and the no-overwrite/skip behavior is covered. However, the two required inputs remain undefined in both schema and description, which is a notable gap for an agent trying to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description says nothing about what 'uuids' or 'destination' mean or require (e.g., whether the folder must exist, whether UUIDs come from search_photos). For a 2-parameter tool with no schema documentation, the description should compensate but does not.

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?

States a specific verb and resource ('Copy photos to a folder') and adds the scope detail that edited versions are preferred where they exist. This clearly distinguishes it from siblings like search_photos or get_photo, which retrieve rather than export.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes agents needing more control to run_osxphotos with the export command, which is a real alternative among the siblings. It does not spell out when to prefer this tool over that one beyond 'more control', leaving some inference to the agent.

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