Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

list_albums

List the user's albums (album_key, title, created), or pass album_key to list the items inside that 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>"
    },
    "name": "list_albums"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_keyNoOptional: list the items of this album.
page_tokenNonext_page_token from the previous call.
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

B3.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It reveals the returned album fields, but says nothing about pagination (page_token is present in the schema but unexplained in prose), permissions on the Google account, or the notification_message follow-up behavior, leaving key operational traits undisclosed.

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?

One sentence, front-loaded with the primary behavior and the field list, with the alternate mode appended economically. No redundant or filler wording.

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 simple list tool with no output schema and fully described parameters, the definition covers the core call patterns adequately. The main gap is that pagination and the notification_message fallback behavior are left entirely to the schema, which is acceptable since the schema is thorough.

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 coverage is 100%, so all four parameters including google_account_email and page_token are already documented in structured form. The description restates the album_key mode switch, which the schema already explains, and adds no new semantics beyond it; 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?

States a specific verb and resource ('List the user's albums') and names the returned fields (album_key, title, created), plus a second mode when album_key is supplied. It does not explicitly contrast with siblings like list_media or get_media, so an agent must infer which lister to pick.

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 description gives conditional guidance for the second mode ('pass album_key to list the items inside that album'), which is genuinely useful. It says nothing about when to choose this over list_media or get_media, and no when-not conditions are stated.

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