Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

get_media

Full metadata for one item: filename, taken time and timezone offset, file size, dimensions, photo/video and duration, camera make/model/aperture/ISO/exposure when present, face count and named people, favorite flag, location (latitude/longitude from the file's GPS plus Google's place name; null when the item has none), plus thumbnail and original download URLs (those need the session: use download_media for bytes).

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>",
      "media_key": "<media_key>"
    },
    "name": "get_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_keyYesOne library media key (AF1Qip...).
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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does useful work: it discloses nullability ("location ... null when the item has none"), conditional fields (camera data "when present""), and a session dependency for download URLs. It stops short of stating that this is a read-only operation, whether trashed/archived items are visible, or what happens with an invalid media_key.

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?

Front-loaded with the core purpose in the first clause, then a dense field inventory tailored to a metadata tool. The single run-on sentence with stacked parentheticals is slightly heavy but contains no filler sentences.

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?

With no output schema, the description correctly takes on the return-value burden and covers the field set, null semantics, and the URL/session caveat, which is enough to call it confidently. It omits error and visibility behavior (invalid key, trashed items), which is the remaining gap for a metadata read.

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 media_key and google_account_email are already documented in the schema, including the 'call list_accounts first' instruction. The description adds no parameter-level meaning and never references notification_message, so the baseline 3 holds.

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 ("Full metadata for one item") and enumerates exactly which fields are returned, including camera data, faces, favorite flag, and location. This makes it clearly distinguishable from download_media and the list/search siblings without opening any 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 routes binary retrieval to download_media ("those need the session: use download_media for bytes"), which is a real alternative and exclusion. It does not say how to obtain a media_key (e.g., via list_media/search_media), leaving that discovery step implicit.

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