Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_upload_file

Upload a local file to Google Drive, choosing a folder or name, and optionally convert .docx/.xlsx/.csv/.pptx/.txt files into native Google Docs, Sheets, or Slides.

Instructions

Upload a local file to Drive. Set convert=true to turn .docx/.xlsx/.csv/.pptx/.txt into native Google Docs/Sheets/Slides.

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": {
      "localPath": "<localPath>"
    },
    "name": "drive_upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
convertNo
folderIdNoroot
localPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive write, so the safety profile is covered. The description adds genuinely useful behavior: the convert flag transforms file formats into native Google types. However, it omits overwrite/duplicate-name behavior, size limits, and what the caller gets back (file ID or URL) — meaningful gaps for an upload tool.

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 sentences, zero filler, with the core action front-loaded and the non-obvious option immediately after. Nothing is redundant with the title or restates the name.

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?

For a four-parameter write tool with no output schema, the definition covers the essential mechanics of uploading and converting but leaves return value, naming defaults, and conflict behavior unstated. An agent could call it correctly for the happy path but would be guessing at the edges.

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 0%, so the description must carry parameter meaning. It does well for `convert`, spelling out the accepted extensions and the resulting native types, but says nothing about `localPath` (path base, relative vs absolute), `name` (defaults to filename?), or `folderId` (defaults to root per schema). Roughly half the parameters remain unexplained.

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 leads with a specific verb and resource ("Upload a local file to Drive"), which is unambiguous and clearly distinct from the read/download-oriented siblings. It stops short of explicitly contrasting itself with any named alternative, but the action is unmistakable.

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?

Usage is only implied: an agent can infer this is the tool for pushing a local file into Drive. There is no statement of prerequisites (auth scopes, target folder must exist), no when-not-to-use guidance, and no mention of how this relates to drive_copy or drive_create_folder for related workflows.

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