Skip to main content
Glama
dipseth

google-workspace-unlimited

Upload Photos

upload_photos

Batch upload photos to Google Photos, optionally adding them to an existing or new album with descriptions.

Instructions

Upload one or more photos to Google Photos with batch optimization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
album_idNoID of existing album to add photos to.
file_pathsYesSingle file path (str) or list of file paths to upload. Required.
descriptionNoDescription for photos (applies to single photo or all in batch).
create_albumNoName of new album to create and add photos to.
user_google_emailNoThe user's Google email address for Photos access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if operation failed
failedNoList of failed uploads with error information
successNoWhether the overall upload operation succeeded
album_idNoAlbum ID where photos were uploaded (if specified)
successfulNoList of successfully uploaded photos with their details
user_emailNoEmail address of the user who uploaded the photos
total_countNoTotal number of files processed
failed_countNoNumber of failed uploads
text_summaryNoHuman-readable summary of the upload operation
successful_countNoNumber of successfully uploaded files
created_album_nameNoName of newly created album (if a new album was created)
upload_time_secondsNoTotal time taken for the upload operation in seconds
Behavior2/5

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

Annotations indicate modification (readOnlyHint false) and side effects (openWorldHint true), but description adds no behavioral details like authentication needs, rate limits, or partial failure handling. The phrase 'batch optimization' is vague. More context needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise but lacks structure. It covers the basic action but could include more useful information without significant length increase.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, output schema existence, and multiple sibling tools, the description lacks completeness. It does not explain return values, error conditions, or when batch optimization applies. Minimal context.

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 baseline is 3. Description adds no additional parameter context beyond the schema. No extra meaning or formatting hints provided.

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 clearly states the verb 'upload', resource 'photos', and target 'Google Photos', with 'batch optimization' hinting at efficiency. It distinguishes from album creation and listing tools but not from 'upload_folder_photos' sibling. Specific and functional.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like upload_folder_photos or create_photos_album. No prerequisites or context provided. The agent must infer usage solely from name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dipseth/google_workspace_fastmcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server