apple-photos-mcp

Overview Schema Source Related Servers Discussions Admin

library-info

Get total counts of photos, movies, albums, folders, keywords, and persons in an Apple Photos library, plus its path and version info.

Instructions

Use when: you want high-level stats about the whole library — total counts of photos, movies, albums, folders, keywords, and persons — or to confirm which library you're targeting before drilling in. Returns: the library path, Photos DB and Photos.app versions, and the six counts. Do not use when: you want the actual albums/keywords/persons rather than just their counts — use list-albums / list-keywords / list-persons; or you want to find specific photos — use query.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`library`	No	Path to a .photoslibrary (default: system Photos library)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`dbVersion`	No
`albumCount`	No
`movieCount`	No
`photoCount`	No
`totalCount`	No
`folderCount`	No
`libraryPath`	No
`personCount`	No
`keywordCount`	No
`photosVersion`	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
```
Changed1 schema field changedv1.1.3Jun 30, 2026
- addedInput schema / properties / library / maxLength
```
Added value: +4096
```

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": {
+    "albumCount": {
+      "type": "number"
+    },
+    "dbVersion": {
+      "type": "string"
+    },
+    "folderCount": {
+      "type": "number"
+    },
+    "keywordCount": {
+      "type": "number"
+    },
+    "libraryPath": {
+      "type": "string"
+    },
+    "movieCount": {
+      "type": "number"
+    },
+    "personCount": {
+      "type": "number"
+    },
+    "photoCount": {
+      "type": "number"
+    },
+    "photosVersion": {
+      "type": [
+        "string",
+        "number"
+      ]
+    },
+    "totalCount": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.4May 26, 2026

TDQS

A4.3/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 of behavioral disclosure. It states exactly what the tool returns (library path, versions, and six counts) and implies it is a read-only operation. It does not disclose any potential side effects or error conditions, but for an info-gathering tool this is acceptable. The description is clear and consistent, with no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections for usage and returns. It is slightly verbose in the 'Do not use' portion, but every sentence serves a purpose. The key purpose is front-loaded, making it easy for an agent to quickly grasp the tool's role.

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

Completeness4/5

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

Given the tool's simplicity (one optional parameter) and the presence of an output schema, the description covers all necessary aspects: purpose, return values, and usage guidance. It does not discuss error handling or performance, but these are not critical for a basic info tool. The description is sufficiently complete for an agent to invoke it 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 coverage is 100% for the single optional parameter (library), and the schema description already includes the default behavior. The tool description does not add new semantic meaning beyond what the schema provides, so the baseline score of 3 applies.

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 explicitly states the tool's purpose: to provide high-level stats about the whole library (total counts of photos, movies, albums, folders, keywords, persons) and to confirm the target library. It clearly distinguishes itself from sibling tools by naming alternatives (list-albums, query) and specifying what it does NOT do.

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 includes explicit 'Use when' and 'Do not use when' sections, listing concrete conditions and naming the specific alternative tools for each exclusion case. This leaves no ambiguity about when to invoke this tool versus others.

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