Skip to main content
Glama
Sign In
Google Workspace MCP VE

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_drive_folder

Create a new folder in Google Drive or a shared drive. Specify the folder name and optional parent folder to organize files.

Instructions

Create a new folder in Drive (or inside a shared drive).

Side effects: creates a folder owned by the authenticated user (or by the shared drive when parent_folder_id lives in one). To upload files into the new folder use create_drive_file with folder_id set to the returned ID. Requires the drive.file OAuth scope.

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": {
      "user_google_email": "<user_google_email>",
      "folder_name": "<folder_name>"
    },
    "name": "create_drive_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
folder_nameYesDisplay name for the new folder. Forward slashes are treated as literal characters, not nesting.
parent_folder_idNoParent folder ID. "root" for My Drive root, or a folder ID within a shared drive for shared-drive folders.root

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.0
    • changedInput schema / properties / folder_name / description
      Previous value: -"The name for the new folder."New value: +"Display name for the new folder. Forward slashes are\ntreated as literal characters, not nesting."
    • changedInput schema / properties / parent_folder_id / description
      Previous value: -"The ID of the parent folder. Defaults to 'root'.\nFor shared drives, use a folder ID within that shared drive."New value: +"Parent folder ID. \"root\" for My Drive root, or a\nfolder ID within a shared drive for shared-drive folders."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description discloses ownership side effects, relationship to create_drive_file, and OAuth scope requirement. Does not mention error conditions or rate limits, but sufficient for a creation tool.

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 concise sentences, front-loaded with the primary action. Every sentence adds necessary context without redundancy.

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?

Explains purpose, side effects, and next steps. Implies return value (ID) but does not detail the output schema. Slightly incomplete for a tool with output schema.

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 100%, so the description adds value by explaining ownership implications of parent_folder_id and clarifying that forward slashes in folder_name are literal. This goes 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?

The description clearly states 'Create a new folder in Drive (or inside a shared drive)', specifying the verb and resource. It distinguishes from sibling tools like create_drive_file by mentioning folder creation and shared drive context.

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?

Describes side effects (ownership) and explicitly directs to use create_drive_file for uploading files, indicating when to use this tool vs alternatives. Mentions required OAuth scope but lacks explicit 'when not to use' guidance.

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