grr

Overview Schema Source Related Servers Discussions Admin

drive.drives.update

Update a shared drive's metadata—such as name, color, theme, or restrictions—by submitting a JSON Drive object through the Drive API.

Instructions

Updates the metadata for a shared drive. For more information, see Manage shared drives [HTTP PATCH] — updates the resource; 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: create, delete, get, hide, list, unhide.

Input Schema

Name	Required	Description	Default
`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.
`driveId`	Yes	[URL path segment] The ID of the shared drive.
`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.
`request_body`	No	Request body of type Drive: pass it via `params` (merged into the built body) or whole via `body_file`.
`useDomainAdminAccess`	No	[query parameter] Issue the request as a domain administrator; if set to true, then the requester will be granted access if they are an administrator of the domain to which the s	false

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"
+}

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / driveId / description

Previous value: -"The ID of the shared drive."New value: +"[URL path segment] The ID of the shared drive."

addedInput schema / properties / useDomainAdminAccess / default
```
Added value: +"false"
```

changedInput schema / properties / useDomainAdminAccess / description

Previous value: -"Issue the request as a domain administrator; if set to true, then the requester will be granted access if they are an administrator of the domain to which the s"New value: +"[query parameter] Issue the request as a domain administrator; if set to true, then the requester will be granted access if they are an administrator of the domain to which the s"

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.5/5.0

Behavior3/5

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

With no annotations, the description does disclose useful behavior: it is an HTTP PATCH, it returns the API response resource as JSON, and it is refused under --readonly safety profiles. However, it does not state permission requirements, whether unmentioned fields remain unchanged, or the reversibility/side effects of updating drive metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description then becomes a dense run-on covering documentation links, HTTP method, readonly refusal, return format, body field names, and sibling tools. Some of that detail, especially the partial body-field list, duplicates the schema and makes the entry less scannable.

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?

The description covers purpose, method, readonly refusal, return type, and body-passing options, which is reasonable given a rich schema and an output schema. But for a metadata mutation with no annotations, it should say more about authorization requirements and what exactly happens to unspecified fields during the patch.

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 description coverage is 100%, so parameter meanings are already fully documented in the schema. The description adds some context about passing a JSON Drive body via `params` or `body_file`, but this largely repeats existing schema descriptions and does not significantly deepen parameter semantics.

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 and resource: 'Updates the metadata for a shared drive.' It also names the sibling operations over the same resource, so an agent can identify this as the update operation distinct from create, delete, get, hide, list, and unhide.

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 states one important usage constraint: the call is refused under --readonly safety profiles. It also lists sibling tools, but does not explicitly say when to choose update versus those alternatives or what prerequisites are required beyond the schema's useDomainAdminAccess parameter.

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

Deploy Server