Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

download_media

Save the bytes of a thumbnail at any size or the original file to a local folder and return the path (plus sha256, and base64 for small files when asked). The image URLs need the signed-in cookies, so always fetch through this tool.

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

Input Schema

NameRequiredDescriptionDefault
sizeNooriginal for the uploaded file (photo or video, byte-exact), or a size spec such as w512-h512, s1024, w2048-h2048-no for an image/thumbnail. Default w512-h512.
media_keyYesOne library media key.
output_dirNoLocal folder to save into. Default: <tmp>/google_photos_downloads.
return_base64Notrue to also inline the bytes (files up to 1.5 MB).
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/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the auth/cookie requirement, the side effect of writing to a local folder, the return contents (path, sha256), and the conditional base64 inlining for small files. It omits overwrite/collision behavior for existing files and any rate-limit or failure semantics.

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 sentences, front-loaded with what is produced and where it lands, then the critical auth constraint. Every clause earns its place with no restatement of the name or title.

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 six-parameter tool with no output schema and no annotations, the description usefully describes the return shape and the auth prerequisite, filling the biggest gaps. Remaining gaps (overwrite policy, size limits beyond the schema's 1.5 MB note, error behavior) are modest.

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 schema already documents size, output_dir, return_base64, and the account email. The phrase 'at any size or the original file' reinforces the size parameter's two modes but adds little beyond the schema text; 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?

The description gives a concrete verb+resource ('Save the bytes of a thumbnail ... or the original file to a local folder') and names the return payload (path, sha256, optional base64), which separates it from metadata siblings like get_media or list_media. It stops short of naming a specific sibling it replaces, so differentiation is implied rather than explicit.

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?

'The image URLs need the signed-in cookies, so always fetch through this tool' is an explicit routing rule that tells the agent not to fetch media URLs directly. There is no stated when-not case or named alternative tool, but the operative condition for choosing this tool is unambiguous.

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