Skip to main content
Glama

Google_drive

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Drive Create File

drive_create_file
Idempotent

Create a new file in Drive with specified name, content, and type (e.g., 'text/plain', 'application/pdf'). Returns the file ID for future reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new file
contentYesText content of the file
mime_typeYesMIME type of the file (e.g., "text/plain", "application/json", "text/html")
parent_folder_idNoID of the parent folder (optional, defaults to root)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of the newly created file
nameNoName of the created file
errorNoError code if connection failed
messageNoError message with instructions
mimeTypeNoMIME type of the created file
webViewLinkNoURL to open file in Google Drive web interface

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Error code if connection failed",
+      "type": "string"
+    },
+    "id": {
+      "description": "ID of the newly created file",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message with instructions",
+      "type": "string"
+    },
+    "mimeType": {
+      "description": "MIME type of the created file",
+      "type": "string"
+    },
+    "name": {
+      "description": "Name of the created file",
+      "type": "string"
+    },
+    "webViewLink": {
+      "description": "URL to open file in Google Drive web interface",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "content": "Q4 Planning Meeting\n- Review sales targets\n- Budget allocation",
+    "mime_type": "text/plain",
+    "name": "meeting_notes.txt"
+  },
+  {
+    "content": "{\"key\": \"value\"}",
+    "mime_type": "application/json",
+    "name": "data.json",
+    "parent_folder_id": "0a1b2c3d4e5f6g7h8i9j"
+  }
+]
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already indicate non-destructive, mutable, idempotent behavior. Description adds return value info but does not disclose file overwrite behavior or permissions needs, adding minimal new context.

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 concise sentences: one for action, one for output. No redundant information.

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?

Adequately describes creation and return of file ID. Could mention default root folder behavior or file size limits, but output schema likely covers return structure.

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% with detailed descriptions for each parameter. The description provides examples but no additional semantic meaning beyond the schema.

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?

Description clearly states 'Create a new file in Drive' with specific parameters (name, content, type), distinguishing from sibling tools that list, get, or search files.

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?

No guidance on when to use this tool versus alternatives like drive_get_file or drive_list_files. No mention of prerequisites or context-dependent usage.

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

All Google_drive toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources