Skip to main content
Glama
Sign In
photos-mcp

photos-mcp

by benjamin-di
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Show photos

photos_show
Read-onlyIdempotent

Display selected photos as a gallery with thumbnails, dates, captions, and links to open each in Google Photos. Use when presenting photos you found.

Instructions

Show photos to the person as a gallery: thumbnail, date, your note and a link that opens each one in Google Photos (claude.ai and ChatGPT draw it; other clients get the same data as JSON). Use it whenever you present photos you picked or found.

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": {
      "items": "<items>"
    },
    "name": "photos_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesPhotos to show, in order
titleNoHeading above the gallery

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.3

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description explains client-dependent rendering: claude.ai and ChatGPT draw a gallery, while other clients receive the same data as JSON. It also discloses the link target and visible gallery fields, which is valuable behavioral context for a read-only presentation 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 definition is two compact sentences and front-loads the core action and output format. The second sentence adds a clear usage trigger without unnecessary repetition.

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?

For a two-parameter, read-only display tool with full schema coverage and no output schema, the description covers the essential behavior: what is shown, how different clients render it, and when to use it. No critical context is missing for correct invocation.

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 parameters are already well documented. The description mentions the note and gallery concept but adds little specific meaning about the items array structure or the title parameter 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 states a specific verb and resource: showing photos as a gallery with thumbnails, dates, notes, and Google Photos links. It is clearer than a generic 'view photos' tool, but it does not explicitly distinguish itself from siblings such as photos_view or photos_contact_sheet.

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

Usage Guidelines4/5

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

It gives a clear trigger: 'Use it whenever you present photos you picked or found.' That tells the agent when this tool is appropriate, though it does not name exclusions or compare against sibling presentation tools.

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