Skip to main content
Glama
sweetrb

apple-photos-mcp

by sweetrb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list-albums

Retrieve album catalog with titles, folder paths, photo counts, shared status, and UUIDs to identify exact album names before filtering queries.

Instructions

Use when: you want the catalog of albums — e.g. to discover exact album names before filtering query by album, or to browse the library's organization. Returns: every album's title, folder path, photo count, shared status, and UUID. Do not use when: you want the photos inside an album — use query with the album filter; you want the folder hierarchy rather than albums — use list-folders; or you just want a total album count — use library-info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
libraryNoPath to a .photoslibrary (default: system Photos library)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
albumsNo

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. Changed1 schema field changedv1.1.3
    • addedInput schema / properties / library / maxLength
      Added value: +4096
  4. Changed1 schema field changedv1.1.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "albums": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  5. First observedv0.1.4

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states the operation returns every album's key fields and implies a read-only listing, but it does not mention edge cases such as empty libraries, permission issues, or default library behavior. Still, the disclosed behavior is sufficiently clear for this tool.

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?

The description is tightly structured with 'Use when', 'Returns', and 'Do not use when' sections, making it scannable and front-loaded. Every sentence contributes actionable information without redundancy.

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?

The description covers what the tool returns, when to use it, when not to use it, and which sibling to choose instead. It also has an output schema, so return-value details are further grounded. Nothing critical is missing for an agent to select and invoke this tool correctly.

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?

Schema description coverage is 100%, so the single optional library parameter is already documented in the schema. The tool description does not add additional parameter semantics, but none are necessary given the schema's clarity.

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?

The description states a specific verb and resource: it lists the catalog of albums, and specifies exactly what is returned (title, folder path, photo count, shared status, UUID). It also differentiates itself from related tools like list-folders and query by explicitly naming what it is not.

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?

The 'Use when' section gives concrete scenarios, and the 'Do not use when' section names specific alternatives with reasons, such as using query for photos inside an album and library-info for total album count. This gives an agent unambiguous routing guidance.

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

Deploy Server

Other Tools