grr

Overview Schema Source Related Servers Discussions Admin

drive.drives.create

Creates a shared drive for team file storage. Provide a unique requestId for idempotent creation and optional settings like name and restrictions to set up a new drive.

Instructions

Creates a shared drive. For more information, see Manage shared drives [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON Drive object accepting backgroundImageFile, backgroundImageLink, capabilities, colorRgb, createdTime, hidden, id, kind and 4 more fields; pass it via params or whole via body_file Siblings over the same resource: delete, get, hide, list, unhide, update.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON Drive object.
`requestId`	Yes	[query parameter] Required. An ID, such as a random UUID, which uniquely identifies this user's request for idempotent creation of a shared drive. A repeated request by the same
`request_body`	No	Request body of type Drive: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`name`	No
`hidden`	No
`themeId`	No
`colorRgb`	No
`orgUnitId`	No
`createdTime`	No
`capabilities`	No
`restrictions`	No
`backgroundImageFile`	No
`backgroundImageLink`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON Drive object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type Drive: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "backgroundImageFile": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "width": {
+          "type": "number"
+        },
+        "xCoordinate": {
+          "type": "number"
+        },
+        "yCoordinate": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "backgroundImageLink": {
+      "type": "string"
+    },
+    "capabilities": {
+      "properties": {
+        "canAddChildren": {
+          "type": "boolean"
+        },
+        "canChangeCopyRequiresWriterPermissionRestriction": {
+          "type": "boolean"
+        },
+        "canChangeDomainUsersOnlyRestriction": {
+          "type": "boolean"
+        },
+        "canChangeDownloadRestriction": {
+          "type": "boolean"
+        },
+        "canChangeDriveBackground": {
+          "type": "boolean"
+        },
+        "canChangeDriveMembersOnlyRestriction": {
+          "type": "boolean"
+        },
+        "canChangeSharingFoldersRequiresOrganizerPermissionRestriction": {
+          "type": "boolean"
+        },
+        "canComment": {
+          "type": "boolean"
+        },
+        "canCopy": {
+          "type": "boolean"
+        },
+        "canDeleteChildren": {
+          "type": "boolean"
+        },
+        "canDeleteDrive": {
+          "type": "boolean"
+        },
+        "canDownload": {
+          "type": "boolean"
+        },
+        "canEdit": {
+          "type": "boolean"
+        },
+        "canListChildren": {
+          "type": "boolean"
+        },
+        "canManageMembers": {
+          "type": "boolean"
+        },
+        "canReadRevisions": {
+          "type": "boolean"
+        },
+        "canRename": {
+          "type": "boolean"
+        },
+        "canRenameDrive": {
+          "type": "boolean"
+        },
+        "canResetDriveRestrictions": {
+          "type": "boolean"
+        },
+        "canShare": {
+          "type": "boolean"
+        },
+        "canTrashChildren": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "colorRgb": {
+      "type": "string"
+    },
+    "createdTime": {
+      "type": "string"
+    },
+    "hidden": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "orgUnitId": {
+      "type": "string"
+    },
+    "restrictions": {
+      "properties": {
+        "adminManagedRestrictions": {
+          "type": "boolean"
+        },
+        "copyRequiresWriterPermission": {
+          "type": "boolean"
+        },
+        "domainUsersOnly": {
+          "type": "boolean"
+        },
+        "downloadRestriction": {
+          "properties": {
+            "restrictedForReaders": {
+              "type": "boolean"
+            },
+            "restrictedForWriters": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "driveMembersOnly": {
+          "type": "boolean"
+        },
+        "sharingFoldersRequiresOrganizerPermission": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "themeId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / requestId / description

Previous value: -"Required. An ID, such as a random UUID, which uniquely identifies this user's request for idempotent creation of a shared drive. A repeated request by the same "New value: +"[query parameter] Required. An ID, such as a random UUID, which uniquely identifies this user's request for idempotent creation of a shared drive. A repeated request by the same "

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "backgroundImageFile": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "width": {
+          "type": "number"
+        },
+        "xCoordinate": {
+          "type": "number"
+        },
+        "yCoordinate": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "backgroundImageLink": {
+      "type": "string"
+    },
+    "capabilities": {
+      "properties": {
+        "canAddChildren": {
+          "type": "boolean"
+        },
+        "canChangeCopyRequiresWriterPermissionRestriction": {
+          "type": "boolean"
+        },
+        "canChangeDomainUsersOnlyRestriction": {
+          "type": "boolean"
+        },
+        "canChangeDownloadRestriction": {
+          "type": "boolean"
+        },
+        "canChangeDriveBackground": {
+          "type": "boolean"
+        },
+        "canChangeDriveMembersOnlyRestriction": {
+          "type": "boolean"
+        },
+        "canChangeSharingFoldersRequiresOrganizerPermissionRestriction": {
+          "type": "boolean"
+        },
+        "canComment": {
+          "type": "boolean"
+        },
+        "canCopy": {
+          "type": "boolean"
+        },
+        "canDeleteChildren": {
+          "type": "boolean"
+        },
+        "canDeleteDrive": {
+          "type": "boolean"
+        },
+        "canDownload": {
+          "type": "boolean"
+        },
+        "canEdit": {
+          "type": "boolean"
+        },
+        "canListChildren": {
+          "type": "boolean"
+        },
+        "canManageMembers": {
+          "type": "boolean"
+        },
+        "canReadRevisions": {
+          "type": "boolean"
+        },
+        "canRename": {
+          "type": "boolean"
+        },
+        "canRenameDrive": {
+          "type": "boolean"
+        },
+        "canResetDriveRestrictions": {
+          "type": "boolean"
+        },
+        "canShare": {
+          "type": "boolean"
+        },
+        "canTrashChildren": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "colorRgb": {
+      "type": "string"
+    },
+    "createdTime": {
+      "type": "string"
+    },
+    "hidden": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "orgUnitId": {
+      "type": "string"
+    },
+    "restrictions": {
+      "properties": {
+        "adminManagedRestrictions": {
+          "type": "boolean"
+        },
+        "copyRequiresWriterPermission": {
+          "type": "boolean"
+        },
+        "domainUsersOnly": {
+          "type": "boolean"
+        },
+        "downloadRestriction": {
+          "properties": {
+            "restrictedForReaders": {
+              "type": "boolean"
+            },
+            "restrictedForWriters": {
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "driveMembersOnly": {
+          "type": "boolean"
+        },
+        "sharingFoldersRequiresOrganizerPermission": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "themeId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the burden and largely does: it declares the operation is an HTTP POST that mutates, that it is refused under readonly safety profiles, and that it returns the API's response resource as JSON. It omits required permission scope and was only able to rely on the requestId schema field for idempotency, keeping it from a 5.

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?

The core purpose is front-loaded in the first sentence, and the remaining detail (HTTP verb, safety profile, return format, body construction, siblings) is dense but relevant. A few clauses run together ('and 4 more fields; pass it via...') but overall it earns its length.

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?

An output schema exists, so return values needn't be explained, and the description covers body construction paths, the safety-profile constraint, and sibling routing. An agent has enough to invoke it correctly; only explicit permission prerequisites are missing.

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%, so the schema documents all six parameters and the body fields. The description adds modest value by explaining the body is a JSON Drive object usable via `params` or whole via `body_file`, but otherwise restates what the schema already provides. Baseline 3 is appropriate.

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 opens with a specific verb+resource ("Creates a shared drive") and even enumerates the sibling operations over the same resource (delete, get, hide, list, unhide, update). An agent can distinguish this from the get/list/update siblings without opening any schema.

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?

It lists sibling tools over the same resource and notes it is refused under --readonly safety profiles, which implies when it can/can't run. However, it never explicitly states when to choose create vs. the alternatives; the routing is left to inference from the operation names.

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

Deploy Server