Skip to main content
Glama
dipseth

google-workspace-unlimited

Google Drive File/Folder Upload (Unified Auth)

upload_to_drive

Upload a file or folder from your filesystem to Google Drive. Specify a target folder and optional custom filename.

Instructions

Upload a file to Google Drive. By default path is the server's local filesystem (single call, supports folders). On remote deployments where the client and server are on different machines, set DRIVE_UPLOAD_CLIENT_FS=true: path is then the client's filesystem — the first call returns a pendingUpload payload with a signed PUT URL; the client uploads bytes to that URL, then re-calls this tool with the same path to finalize the Drive upload. Folder uploads are only supported in server-FS mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoLocal filesystem path to the file or folder to upload (supports ~ expansion)
filenameNoCustom filename for the uploaded file (optional - uses original filename if not provided)
folder_idNoGoogle Drive folder ID where file will be uploaded (default: 'root' for root folder)root
user_google_emailNoThe user's Google email address for Drive access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
messageNo
successNo
fileInfoNo
warningsNo
userEmailNo
filesUploadedNo
folderSummaryNo
pendingUploadNo
Behavior5/5

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

The description goes far beyond annotations, detailing the two-step client-FS process (pendingUpload with signed PUT URL, then re-call to finalize), folder upload limitations, and the use of environment variable DRIVE_UPLOAD_CLIENT_FS. Annotations only indicate readOnlyHint=false, so this adds critical behavioral context.

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?

The description is fairly concise given the complexity, with two focused paragraphs. The main action is front-loaded, and mode-specific details follow logically. Slight improvement could be made by separating modes more clearly.

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

Completeness5/5

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

With an output schema present, the description does not need to detail return values. It covers all key aspects: input modes, constraints (folder uploads only in server-FS), and the client-FS workflow. This is comprehensive for such a behavior-rich tool.

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% with descriptions for all 4 parameters. The description adds context about how 'path' works differently in each mode and the auto-injection of user_google_email, but the schema already provides adequate semantics.

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 'Upload a file to Google Drive' and explains the dual-mode behavior (server vs client filesystem), making the tool's purpose very specific and distinct from sibling tools like upload_photos or create_drive_file.

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 description provides clear context on when to use server-FS vs client-FS modes (based on deployment) and notes that folder uploads are only supported in server-FS mode. However, it does not explicitly mention when to use this tool over alternatives like upload_photos.

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