apple-photos-mcp

Overview Schema Source Related Servers Discussions Admin

list-keywords

Get a sorted list of photo keywords with usage counts to verify tag spellings and identify most-used tags before filtering your library.

Instructions

Use when: you want the catalog of keywords (tags) in the library — e.g. to discover exact keyword spellings before filtering query by keyword, or to see which tags are most used. Pass limit for the top-N. Returns: keywords with their photo counts, sorted most-used first. Do not use when: you want photos carrying a keyword — use query with the keyword filter; or you want people/faces rather than tags — use list-persons.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Top-N keywords
`library`	No	Path to a .photoslibrary (default: system Photos library)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`keywords`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.13Sep 24, 2026

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"

Changed1 schema field changedv2.1.9Aug 7, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
Changed2 schema fields changedv1.1.3Jun 30, 2026
- addedInput schema / properties / library / maxLength
```
Added value: +4096
```
- addedInput schema / properties / limit / maximum
```
Added value: +100000
```

Changed1 schema field changedv1.1.0Jun 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "keywords": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.4May 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the return format (keywords with photo counts, sorted most-used first) and the effect of the limit parameter. While it doesn't explicitly state it is read-only, the list operation implies no side effects, which is adequate given the tool's nature.

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 well-structured with clear sections: 'Use when', 'Returns', and 'Do not use when'. It is concise, front-loaded with the primary use case, and every sentence adds value 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 tool has only two optional parameters, both well-documented in the schema. The description provides usage context, exclusions, and return format. Since an output schema exists, the description need not detail the return structure further. It is fully sufficient for an agent to correctly invoke the tool.

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?

The input schema has 100% description coverage for both parameters. The description adds minor context for limit ('top-N') but does not go beyond the schema's own description. Since the schema already documents the parameters well, the description adds limited value, warranting the baseline score of 3.

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 clearly states the tool lists the catalog of keywords/tags in the library, with a specific verb and resource. It distinguishes itself from siblings like list-persons and query by explicitly naming what it does not do, making its purpose unambiguous.

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 description provides explicit 'Use when' and 'Do not use when' guidance, naming alternatives (query for photos by keyword, list-persons for people/faces). This directly tells an agent when to select this tool versus its siblings.

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