photos-mcp

Photos Contact Sheet

photos_contact_sheet

Read-onlyIdempotent

Builds a single numbered JPEG grid of up to 24 Google Photos items, adding play badges for videos and a legend that maps each number to its ID and date.

Instructions

One JPEG grid (at most 1568 px) of up to 24 items with numbered tiles and a play badge on videos, plus a legend mapping each number to its id and date.

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": {
      "ids": "<ids>"
    },
    "name": "photos_contact_sheet"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Item ids (max 24)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.3Oct 27, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely useful behavioral context beyond that: the output is a single JPEG capped at 1568 px, tiles are numbered, videos get a play badge, and a legend maps numbers to ids and dates. It doesn't cover error cases or what happens above 24 items, but the added context is substantial.

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?

A single dense sentence that front-loads the output format and enumerates the key visual features without waste. Slightly fragmentary but efficient for the amount of information delivered.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so thoroughly (grid, size cap, numbering, badges, legend). Only the usage context and edge-case behavior are missing, which is minor for a single-parameter 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?

Schema coverage is 100% with a single self-documented 'ids' parameter (max 24), so the schema does the heavy lifting. The description reinforces the 24-item cap and explains that each id surfaces in the legend, but adds no new syntax or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly conveys that this tool produces a single JPEG contact-sheet image composed of numbered tiles with a legend, which is specific and distinct from the view/get/list siblings. The verb is implied ('produce a grid') rather than stated, since the description focuses on the output artifact, but the resource and effect are unambiguous.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this tool versus alternatives like photos_view or photos_show, nor any prerequisites or exclusions. The agent must infer from the output description that this is a batch-preview generator.

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

Deploy Server