Skip to main content
Glama
Sign In
drive-mcp

drive-mcp

by reisbel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

upload_file

Upload a local file to Google Drive, optionally converting it to a Google Doc, Sheet, or Slides format by specifying the target type.

Instructions

WRITES. Upload a local file. With convertTo the upload is imported as a Google-native file (e.g. a .docx or .md into a Google Doc, a .csv or .xlsx into a Sheet).

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": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName in Drive. Default: the local file name.
folderIdNoParent folder. Default My Drive root.
mimeTypeNoMIME type of the local file. Guessed from the extension when omitted.
convertToNo
localPathYesAbsolute path of the file to upload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. The leading 'WRITES.' correctly signals a mutating operation, and it usefully explains that convertTo imports into a Google-native type. However, it omits permission requirements, overwrite/collision behavior, and any indication of what the call returns.

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?

Three compact sentences, front-loaded with the mutating nature via 'WRITES.' and then the core action. Nearly every phrase earns its place, with only the terse 'WRITES.' banner being slightly cryptic in isolation.

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 five-parameter write tool with no annotations and no output schema, the description covers the conversion nuance well but leaves out permissions, name-collision behavior, and return value. Adequate but with clear gaps an agent would want before invoking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3, but the description adds real meaning for convertTo (which has no schema description) by explaining that it imports into a Google-native document/spreadsheet/presentation with format examples. This exceeds the schema's bare enum for the most consequential parameter.

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 states a specific verb and resource ('Upload a local file') and clarifies the conversion behavior with concrete format examples. It is clear what the tool does, though it never explicitly distinguishes itself from the sibling 'create_file', leaving the upload-vs-create boundary to inference.

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?

There is no explicit when-to-use guidance and no comparison against alternatives such as create_file or copy_file. Usage is only implied by the phrase 'Upload a local file', so an agent must infer the selecting condition itself.

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

Deploy Server

Other Tools