Skip to main content
Glama
dipseth

google-workspace-unlimited

Upload Folder Photos

upload_folder_photos

Upload all photos from a local folder to Google Photos, with optional recursion into subfolders and album creation or assignment to an existing album.

Instructions

Upload all photos from a folder (with optional recursion) to Google Photos

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
album_idNoID of existing album to add photos to.
recursiveNoWhether to include subfolders. Defaults to True.
folder_pathYesLocal path to folder containing photos. Required.
create_albumNoName of new album to create for these photos.
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 folder upload operation succeeded
album_idNoAlbum ID where photos were uploaded (if specified)
recursiveNoWhether subfolders were included
successfulNoList of successfully uploaded photos with details
user_emailNoEmail address of the user
folder_pathYesLocal folder path that was uploaded
total_foundNoTotal number of photo files found in the folder
failed_countNoNumber of failed uploads
text_summaryNoHuman-readable upload summary
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
success_rate_percentNoPercentage of successful uploads
Behavior3/5

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

Annotations indicate it is not read-only, which is consistent with the upload action. The description adds the behavior of uploading all photos from a folder with optional recursion, but does not disclose potential side effects like album creation, permission requirements, or handling of non-image files. With annotations present, the description adds moderate context.

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 a single, concise sentence of 13 words that is front-loaded with the key action. It contains no waste or redundancy.

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

Completeness3/5

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

The description is brief and covers the main action, but for a potentially heavy operation like uploading a folder with recursion, it lacks details on authentication handling, performance implications, file type filtering, and return value structure (though output schema exists). It is adequate but not thorough.

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. The description reiterates 'folder' and 'recursion' but adds no semantic detail beyond the schema for individual parameters. It does not explain parameter formats or interdependencies.

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?

The description clearly states the action (upload), the resource (all photos from a folder), and the target (Google Photos), with mention of optional recursion. It effectively distinguishes from sibling tools like 'upload_photos' which likely handles individual photos.

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?

The description does not provide any guidance on when to use this tool versus alternatives such as 'upload_photos' or 'list_photos_albums'. Sibling tools exist but no when-to-use or when-not-to-use context is given.

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