Skip to main content
Glama
navidmoazzez

Google Photos MCP

by navidmoazzez

Add a caption, location or map to an album

add_album_enrichment

Insert captions, named locations, or maps between photos in an album, turning a photo grid into a narrated story. Place at the end or after any specific photo.

Instructions

Insert an enrichment into an album: a text caption, a named location, or a map between two places. Enrichments sit between photos and are how an album reads as a story rather than a grid.

Position defaults to the end of the album.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoFor type 'text': the caption.
typeYesWhat to add.
accountNoWhich connected Google account to act as, by the name it was configured under (or its email). Defaults to the first one. Call list_accounts to see them.
album_idYesThe album to enrich.
latitudeNoFor type 'location': latitude.
longitudeNoFor type 'location': longitude.
origin_nameNoFor type 'map': the starting place name.
location_nameNoFor type 'location': the place name to show.
origin_latitudeNoFor type 'map': starting latitude.
destination_nameNoFor type 'map': the ending place name.
origin_longitudeNoFor type 'map': starting longitude.
after_media_item_idNoPlace the enrichment after this item. Omit to put it at the end of the album.
destination_latitudeNoFor type 'map': ending latitude.
destination_longitudeNoFor type 'map': ending longitude.
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already convey mutability and non-destructiveness; the description adds behavior beyond them by explaining that enrichments occupy sposition between photos and that position defaults to the album end. This helps an agent anticipate placement semantics without contradicting the annotations.

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?

Two short sentences, front-loaded with the core action and enrichment types, then a single high-value positional default. No flff or repetition of schema content.

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?

For a write tool with no output schema, the description covers the conceptual purpose, the three type variants, and the one non-obvious behavioral default. It does not explain return values, but this is a minor gap for an insert operation with a fully self-describing schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the paramter baseline is 3. The description adds semantic value by explicitly stating the default placement behavior of after_media_item_id, which is useful for constructing a valid invocation.

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?

Names a specific operation, 'Insert an enrichment into an album,' and enumerates the three concrete enrichment kinds: text caption, named location, or map between places. The phrase 'enrichments sit between photos' implicitly separates this from sibling tools that add media to albums.

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?

Provides clear context about when this tool makes sense (adding storytelling elements between photos) even though it does not explicitly name sibling alternatives or exclusions. The positional default notes how the insertion behaves, which is actionable guidance.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/navidmoazzez/google-photos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server