Skip to main content
Glama

Photos Album Add

photos_album_add
Idempotent

Add up to 50 photo or video IDs from search or list results to an album, including shared albums the account can edit, without duplicating existing items.

Instructions

Add up to 50 items (ids from search or list) to an album, also a shared one this account may add to. Items already in it stay once. Returns the album as Google shows it afterwards and added (from its counts before and after).

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

Input Schema

NameRequiredDescriptionDefault
idsYesItem ids (max 50)
album_idYesAn album id from photos_albums

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.3

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the 50-item cap, the duplicate policy ('items already in it stay once'), the shared-album permission caveat, and the return shape ('album as Google shows it afterwards and added'). The idempotent/non-destructive safety profile is already covered by annotations, so this extra context is the description's main contribution.

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?

Single compact passage with the cap and the duplicate rule front-loaded, and no filler sentences. The odd line break inside 'may\nadd to' is a formatting blemish rather than a content problem.

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 annotations covering safety and idempotency and an output schema covering the return value, the description supplies the remaining essentials: item limit, duplicate handling, and shared-album permission. Only an explicit note on failure modes (e.g., permission denied, invalid ids) is missing.

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 coverage is 100%, so the baseline is 3; the description earns above baseline by giving provenance for `ids` ('from search or list'), which the schema does not say. The max-50 restatement duplicates `maxItems` and `album_id` provenance is already in the schema.

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?

States a specific verb and resource ('Add ... items ... to an album') and immediately scopes it against siblings by naming where the ids come from ('ids from search or list') and distinguishing it from album creation/removal tools. An agent can tell exactly what this does without opening the schema.

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?

Points to the upstream tools that supply ids ('search or list') and notes it works on a shared album 'this account may add to', which effectively states a permission precondition. It does not explicitly say when to use photos_album_remove or photos_album_create instead, so routing is implied rather than spelled out.

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