Google MCP

Overview Schema Source Related Servers Discussions Admin

upload_file

Creates a new Google Drive file from a local file up to 100 MB, optionally converting documents or spreadsheets, with a default mcp_default folder.

Instructions

Create a new Drive file from a local file (up to 100 MB); this reads the given local file. Defaults to the app-created mcp_default folder at the My Drive root. Writes touch only files the app creates. Use update_file to change a file already uploaded.

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": {
      "path": "<path>"
    },
    "name": "upload_file"
  }
}

Input Schema

Name	Required	Description
`name`	No	Drive file name; defaults to the local file name
`path`	Yes	Absolute local path (~ is expanded); relative paths are rejected; the file to upload
`convert`	No	Convert .md/.txt/.docx to a Google Doc, .csv/.xlsx to a Google Sheet
`folder_id`	No	Parent folder ID; defaults to mcp_default

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description does real work: it discloses the 100 MB limit, that it reads the local file, that writes are scoped to app-created files, and where the file lands by default. It does not address overwrite/duplicate-name behavior or permission requirements, which keeps it from a 5.

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?

Three tight sentences, front-loaded with the core action and size limit, followed by placement and the sibling routing hint. No repetition of schema content and nothing wasted.

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

Completeness4/5

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

For a mutation tool with no annotations and no output schema, the description covers action, source, size cap, destination default, and write scope. It leaves return value and name-collision behavior unstated, which is a minor gap rather than a blocking one.

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 the schema already documents all four parameters clearly. The description adds only the location of the default mcp_default folder (My Drive root) and reinforces that path is read locally; that is a marginal supplement, so the baseline 3 applies.

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?

States a specific verb and resource (create a new Drive file from a local file), adds a size bound, and explicitly contrasts with update_file, so the agent can distinguish it from siblings like download_file or update_file without opening any schema.

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?

It names the alternative for the common confusion case (modifying an uploaded file → update_file) and states the default destination behavior. There is no explicit when-not guidance beyond that single alternative, so it is strong but not exhaustive.

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