Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

upload_media

Upload a local photo or video file (up to 10 GB) into the library, optionally into an album. Sent in resumable chunks, so a dropped connection resumes instead of restarting. Returns the new item. Uploading a file that is already in the library returns the existing item.

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>",
      "file_path": "<file_path>"
    },
    "name": "upload_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
chunk_mbNoChunk size in MB, 1-256. Default 8.
album_keyNoOptional album to add the upload to.
file_nameNoOptional name to store it under (default: the file's own name).
file_pathYesAbsolute path of a local image or video file.
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.8/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 behavioral burden. It usefully discloses the 10 GB size limit, resumable chunked uploads, the return of the new item, and deduplication returning an existing item. It omits authentication and permission details, but those are partially covered by the schema parameter description.

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?

The description is four compact sentences with zero filler. Purpose is front-loaded, followed by resumability, return behavior, and deduplication semantics, each of which earns its place.

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 upload tool with no output schema, the description covers the key operational behavior: size limit, resumable transfers, deduplication, and return value. It leaves authentication and error handling mostly to the schema and related tools, which is acceptable given full schema coverage but keeps it from being fully self-contained.

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 all six parameters, including chunk_mb and album_key, are already documented in the schema. The description only reinforces that the album is optional and the file is local, adding little meaning beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb and resource: uploads a local photo or video file into the library, optionally into an album. It is clear what the tool does, but it does not explicitly name or differentiate from siblings such as add_to_album or download_media, so it falls 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?

The description implies usage when a local media file should be added to the library and notes the deduplication behavior. However, it gives no explicit when-to-use versus when-not-to-use guidance, and it does not name alternatives such as add_to_album for adding existing library items to albums.

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