Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

list_accounts

List the Google accounts signed in to the saved session with their /u// slot. Call first and confirm with the user which email holds their photos.

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": "list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose that accounts come from an already-saved session (so no interactive auth is implied) and that the result includes a /u/<N>/ slot used for later calls. It omits what happens with zero signed-in accounts, whether it can trigger auth, and the human-in-the-loop confirmation semantics of the notification_message parameter.

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 sentences, zero filler, with the core action front-loaded and the follow-up instruction second. Every clause carries information the agent needs.

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 one-optional-param read tool with no output schema and no annotations, the description covers what it returns (accounts plus /u/<N>/ slot) and the required next step. It is nearly complete, lacking only the empty-session/error case and any mention of the notification_message fallback behavior.

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% for the single optional notification_message parameter, so the schema already explains its purpose and formatting constraints. The description adds no meaning about when to supply that message or how it interacts with the 'confirm with the user' step, so baseline 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 ('List') and resource ('Google accounts signed in to the saved session') and adds a distinctive return detail ('their /u/<N>/ slot'). No sibling in the catalog deals with account enumeration, so the purpose is unambiguous and separable from list_albums/list_media/check_session.

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?

Gives explicit ordering guidance ('Call first') and a required workflow step ('confirm with the user which email holds their photos'), which tells the agent both when to invoke it and what to do with the result. It stops short of naming an alternative or stating a when-not condition, so it is not a full 5.

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