Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

add_to_album

Add library items to an existing album.

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": {
      "google_account_email": "<google_account_email>",
      "album_key": "<album_key>",
      "media_keys": "<media_keys>"
    },
    "name": "add_to_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_keyYesAlbum key from list_albums or create_album.
media_keysYesLibrary media keys (AF1Qip...) from list_media / search_media, as a JSON array or comma-separated.
google_account_emailYesThe signed-in Google account email whose Google Photos library to use (e.g. the one at /u/1/). Call list_accounts first and confirm with the user; do not guess.
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it does not meet it. It never says whether adding a duplicate item is idempotent, whether the operation is reversible, what permissions or account scoping are required, or what happens to items already in the album.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity is close to under-specification for a four-parameter mutation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a write operation with no annotations, no output schema, and no statement of result or failure behavior. The one-line description does not cover enough for an agent to call it confidently, especially around duplicate handling and account scoping.

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%, including key formats (AF1Qip...), accepted encodings (JSON array or comma-separated), and account-selection warnings, so the schema does the heavy lifting. The description adds nothing about any of the four parameters; 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 states a specific verb and resource: 'Add library items to an existing album.' The word 'existing' distinguishes it from create_album, and 'Add' distinguishes it from remove_from_album. It does not explicitly name those siblings, so it falls short of a 5.

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?

Beyond the implicit precondition that the album must already exist, the description gives no when-to-use guidance and never points to create_album or remove_from_album. The genuinely useful routing hints ('Album key from list_albums or create_album', 'Call list_accounts first and confirm with the user') live only in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources