Skip to main content
Glama

Photos Albums

photos_albums
Read-onlyIdempotent

List Google Photos albums with pagination, returning id, title, photo count, and shared status so you can choose an album ID to browse its photos.

Instructions

List albums: {id, title, count, shared}. Use an id with photos_list(source="album").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "photos_albums"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page (1-50)
cursorNonext_cursor from the previous page

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.3

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds the field set returned, but with an output schema present that addition largely duplicates structured data, and it says nothing about pagination behavior despite cursor/limit parameters.

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 compact clauses with zero filler; the purpose and the return fields are front-loaded, and the chaining hint follows. Nothing could be removed without losing information.

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 two-optional-parameter list tool with a full output schema and rich annotations, the description covers purpose and follow-up usage adequately. The only gap is that pagination semantics are left entirely to the schema rather than acknowledged in prose.

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 limit ('Items per page (1-50)') and cursor ('next_cursor from the previous page') are already fully documented. The description adds no parameter-level meaning, so the baseline of 3 applies.

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 ('List albums') and enumerates the returned fields '{id, title, count, shared}', which immediately separates it from the mutation siblings (photos_album_add, photos_album_delete) and from photos_search. An agent can tell 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?

Explicitly gives the follow-up path: 'Use an id with photos_list(source="album")', which tells the agent this is a discovery/chaining step rather than a terminal call. It does not state when to prefer it over photos_search or photos_album_* alternatives, so no exclusions are covered.

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