photos-mcp

Photos Get

photos_get

Read-onlyIdempotent

Retrieve detailed metadata for up to 10 Google Photos items in one request, including timestamps, location, camera, dimensions, size, duration, and albums; failed items return their own errors.

Instructions

Details per item, all ids in one Google request: the item shape of photos_search plus uploaded_at (UTC), lat/lon, camera, width/height (original), size_bytes, duration_s and albums. Failed items carry their own error.

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_get"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.3Oct 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral detail beyond annotations: all ids are fetched in one Google request, and failed items carry their own error, which is important for partial-failure handling. It does not describe rate limits or auth requirements, but the added batching and error semantics are meaningful.

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 a single, dense sentence that front-loads the core behavior: per-item details for all ids in one request. It then efficiently lists the added return fields and partial-error behavior without unnecessary filler.

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?

The tool has a simple one-parameter schema, full schema description coverage, annotations covering safety, and an output schema. The description adds batching behavior and partial-failure semantics, making it largely complete for invocation. The main missing piece is explicit routing guidance versus sibling retrieval tools.

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%, and the single ids parameter is already documented in the schema as an array of item ids with max 10 and min 1. The description reinforces batched lookup semantics by saying all ids are sent in one Google request, but it does not add syntax or constraints beyond what the schema provides.

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 states that this tool retrieves per-item details for a batch of ids in one request. It also clarifies the return shape by anchoring it to photos_search plus additional fields, which helps distinguish it from search-style listing tools. However, it does not explicitly differentiate itself from siblings like photos_show or photos_view.

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

Usage Guidelines3/5

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

The usage context is implied: callers should provide item ids and receive detailed metadata for those items in a single request. However, there is no explicit guidance on when to use this versus photos_search, photos_show, photos_view, or photos_list, nor any stated exclusions.

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

Deploy Server