Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

list_media

Page through the Google Photos library timeline, newest first: media key, taken/uploaded time, dimensions, photo or video (+duration), favorite flag and a thumbnail URL. Optional date range (after/before) and type filter. Pass next_page_token to continue.

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_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoOnly items taken on/after this time: YYYY-MM-DD, ISO-8601 UTC, or epoch ms.
beforeNoOnly items taken on/before this time (a bare date includes the whole day).
page_sizeNoTarget number of items, 1-500 (default 100). Google pages in its own chunk sizes, so a call can return somewhat more; keep paging with next_page_token.
media_typeNoFilter by type. Default all.
page_tokenNonext_page_token from the previous list_media 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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose ordering (newest first), the returned fields, and continuation behavior. It says nothing about read-only safety, permission/scope requirements, rate limits, or behavior on empty results, and it names the continuation token 'next_page_token' while the schema calls it 'page_token'.

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?

Three tight sentences: the core operation and payload first, then optional filters, then paging. No filler, and the most important information is front-loaded.

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?

Because there is no output schema, listing the returned fields is valuable and largely compensates. The account-selection prerequisite lives in the schema, but the description still lacks any note on large-library pagination limits or error behavior for a 7-parameter listing tool.

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 the baseline is 3; the description only restates that date range and type are optional filters. It adds no format, default, or interaction detail beyond what the schema already documents for after/before/media_type/page_size.

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?

Specific verb and resource ('Page through the Google Photos library timeline, newest first') plus an enumeration of returned fields, which makes the operation concrete. It is not explicitly distinguished from search_media or get_media, which are the obvious overlapping siblings, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Pagination guidance is given ('Pass next_page_token to continue'), and the optional date-range and type filters imply the browse-style use case. However, there is no statement of when to prefer this over search_media, get_media, or list_albums, so the agent must infer routing.

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