Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

drive_files_create

Create a new file in Google Drive with custom metadata and optional local file upload. Set a name, MIME type, and parent folder to organize and store content.

Instructions

Create a new file in Google Drive. Use with bodyParams for metadata and optionally upload a local file.

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

Input Schema

NameRequiredDescriptionDefault
nameYesFile name
fieldsNoFields to return (e.g. "id,webViewLink")
parentsNoParent folder IDs (JSON array as string, e.g. '["folderId"]')
mimeTypeNoMIME type (e.g. "application/vnd.google-apps.document")
uploadPathNoLocal file path to upload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-idempotent open-world mutation. The description adds only that a local file may be uploaded rather than a metadata-only record. It says nothing about required OAuth scopes, quota/rate limits, or what happens when uploadPath is omitted (empty file vs. folder).

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, front-loaded with the operation, with no filler. The mention of 'bodyParams' is wasted or actively confusing since it maps to no schema field.

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 mutation with full schema coverage and no output schema, the description covers the core action but leaves gaps: it doesn't explain that parents expects a JSON-array string, how mimeType affects the created entity, or what the tool returns. It is adequate to select the tool but thin for invoking it confidently.

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 coverage is 100%, so all five parameters are already documented in the schema and the baseline is 3. However, the description references 'bodyParams', which does not exist in the input schema, which is likely to confuse an agent trying to map the instruction to actual arguments. Beyond that, only the local-file upload hint for uploadPath adds any meaning, and that is already stated in the schema.

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: 'Create a new file in Google Drive.' That is unambiguous about the operation. It doesn't differentiate itself from siblings such as drive_files_copy, docs_create or slides_create, so an agent must infer which creation path applies.

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?

The only usage cue is 'optionally upload a local file,' which implies when uploadPath is relevant. There is no guidance on when to choose this over drive_files_copy, drive_files_update, or the docs/slides creation tools, and no prerequisites or exclusions are stated.

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