Skip to main content
Glama

drive_upload

Upload a file from this workspace's files (by file_id) into a Google Drive folder e.g. a client's receipt or contract. Returns the new file's id and link. The folder must be shared with the workspace's Drive address as Editor (drive.folders shows the address). A folder in a Shared Drive is written by the Drive address; a folder in a personal My Drive needs Google connected in the workspace's integrations (the file is then uploaded as that person and moved in). Files up to 100 MB. Uploading twice creates two files: after outcome_unknown check the folder first.

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": {
      "file_id": "<file_id>",
      "folder": "<folder>"
    },
    "name": "drive_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName in Drive. Default: the file's own name.
folderYesDrive id or pasted link of the destination folder.
file_idYesId of a file in the workspace's files.
mime_typeNoContent type. Default: the stored one.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Substantially exceeds the annotations: annotations only say non-read-only and non-idempotent, while the description explains the actual duplication consequence ('Uploading twice creates two files'), the 100 MB size ceiling, the differing write/impersonation semantics for Shared Drives versus personal My Drive, and the required sharing permission. It also states the return payload (new file id and link). This is exactly the behavioral context an agent needs before a non-idempotent write.

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?

Front-loaded with the core action and return value, then prerequisites, then the duplicate-upload warning in the final position. Every sentence carries information, though the My Drive sentence is dense with nested parentheticals and could be split for faster parsing.

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?

For a non-idempotent external write with no output schema, it covers the source of the input file, destination requirements, permission/credential prerequisites, size limit, duplicate risk and remediation, and the shape of the return value. Nothing an agent needs in order to call it correctly appears missing.

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 the schema already explains name, folder, file_id, mime_type and in_workspace with their defaults. The description adds only the constraint that the folder must be shared as Editor; it doesn't clarify format expectations or interactions between parameters. Baseline 3 is appropriate when the schema carries the meaning.

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?

Names a specific verb and resource with explicit source and destination: upload a file from this workspace's files (by file_id) into a Google Drive folder. The scope is unambiguous, but it never names or rules out near-siblings such as files_upload or drive_import, so the agent must infer the distinction from the source being 'this workspace's files'.

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?

Gives concrete preconditions for use: the destination folder must be shared with the workspace's Drive address as Editor (pointing at drive.folders for that address), and personal My Drive targets require Google connected in integrations. It also gives a recovery rule ('after outcome_unknown check the folder first'). What is missing is an explicit statement of when a different upload tool is the right choice.

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.