Skip to main content
Glama

drive upload file

drive_upload_file

Uploads a local file from the server's download directory to Google Drive, with optional name, MIME type, and parent folder for agent-driven file storage.

Instructions

Upload a local file from the server's download directory into Drive. Write operation.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
mime_typeNo
parent_idNo
local_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so 'Write operation' merely restates structured data. The one genuine addition is the requirement that local_path point inside the download directory, but the description says nothing about non-idempotent behavior (duplicate uploads), name-collision handling, or size/quota limits.

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?

Two short sentences with the operational constraint front-loaded and no padding. The trailing 'Write operation' is largely redundant given the annotations, which keeps it from being maximally efficient.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. But for a four-parameter mutation with 0% schema coverage, the description leaves the optional parameters' defaults and conflict behavior entirely unspecified, which is a notable gap for an agent deciding how to call it.

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

Parameters2/5

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

Schema description coverage is 0%: the four parameters carry only titles and null defaults, so the description must explain meaning. It does not — it never says that 'name' likely defaults to the local filename, that 'mime_type' may be inferred from the file, or that omitting 'parent_id' places the file at the Drive root.

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 (Upload) and resource (a local file into Drive) plus a scope constraint: the source must live in the server's download directory. That constraint also distinguishes it from siblings like drive_copy_file and drive_download_file, which operate on Drive-side content rather than local server files.

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?

The 'from the server's download directory' clause implicitly tells the agent when this tool applies, and the write nature signals it is not a read path. However, there is no explicit comparison to drive_copy_file or drive_move_file, no mention of what to do when a file with the same name already exists, and no stated prerequisites.

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