grr

Overview Schema Source Related Servers Discussions Admin

drive.permissions.update

Update an existing permission on a file or shared drive using patch semantics to change role, expiration, or ownership settings.

Instructions

Updates a permission with patch semantics. For more information, see Share files, folders, and drives. Warning: Concurrent permission modifications (such as update or delete) on the same file, folder, or shared drive aren't supported across any users or clients; only the last update is applied [HTTP PATCH] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON Permission object accepting allowFileDiscovery, deleted, displayName, domain, emailAddress, expirationTime, id, inheritedPermissionsDisabled and 8 more fields; pass it via params or whole via body_file Siblings over the same resource: create, delete, get, list.

Input Schema

Name	Required	Description	Default
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`fileId`	Yes	[URL path segment] The ID of the file or shared drive.
`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 Permission object.
`permissionId`	Yes	[URL path segment] The ID of the permission.
`request_body`	No	Request body of type Permission: pass it via `params` (merged into the built body) or whole via `body_file`.
`removeExpiration`	No	[query parameter] Whether to remove the expiration date.	false
`supportsAllDrives`	No	[query parameter] Whether the requesting application supports both My Drives and shared drives.	false
`transferOwnership`	No	[query parameter] Whether to transfer ownership to the specified user and downgrade the current owner to a writer. This parameter is required as an acknowledgement of the side ef	false
`supportsTeamDrives`	No	[query parameter] Deprecated: Use `supportsAllDrives` instead.	false
`useDomainAdminAccess`	No	[query parameter] Issue the request as a domain administrator. If set to `true`, and if the following additional conditions are met, the requester is granted access: 1. The file	false
`enforceExpansiveAccess`	No	[query parameter] Deprecated: All requests use the expansive access rules.	false

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`role`	No
`type`	No
`view`	No
`domain`	No
`deleted`	No
`photoLink`	No
`displayName`	No
`emailAddress`	No
`pendingOwner`	No
`expirationTime`	No
`permissionDetails`	No
`allowFileDiscovery`	No
`teamDrivePermissionDetails`	No
`inheritedPermissionsDisabled`	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 Permission object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type Permission: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "allowFileDiscovery": {
+      "type": "boolean"
+    },
+    "deleted": {
+      "type": "boolean"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "emailAddress": {
+      "type": "string"
+    },
+    "expirationTime": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "inheritedPermissionsDisabled": {
+      "type": "boolean"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "pendingOwner": {
+      "type": "boolean"
+    },
+    "permissionDetails": {
+      "items": {
+        "properties": {
+          "inherited": {
+            "type": "boolean"
+          },
+          "inheritedFrom": {
+            "type": "string"
+          },
+          "permissionType": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "photoLink": {
+      "type": "string"
+    },
+    "role": {
+      "type": "string"
+    },
+    "teamDrivePermissionDetails": {
+      "items": {
+        "properties": {
+          "inherited": {
+            "type": "boolean"
+          },
+          "inheritedFrom": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          },
+          "teamDrivePermissionType": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type": {
+      "type": "string"
+    },
+    "view": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed15 schema fields changedOct 26, 2026

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

changedInput schema / properties / enforceExpansiveAccess / description

Previous value: -"Deprecated: All requests use the expansive access rules."New value: +"[query parameter] Deprecated: All requests use the expansive access rules."

changedInput schema / properties / fileId / description

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

changedInput schema / properties / permissionId / description

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

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

changedInput schema / properties / removeExpiration / description

Previous value: -"Whether to remove the expiration date."New value: +"[query parameter] Whether to remove the expiration date."

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

changedInput schema / properties / supportsAllDrives / description

Previous value: -"Whether the requesting application supports both My Drives and shared drives."New value: +"[query parameter] Whether the requesting application supports both My Drives and shared drives."

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

changedInput schema / properties / supportsTeamDrives / description

Previous value: -"Deprecated: Use `supportsAllDrives` instead."New value: +"[query parameter] Deprecated: Use `supportsAllDrives` instead."

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

changedInput schema / properties / transferOwnership / description

Previous value: -"Whether to transfer ownership to the specified user and downgrade the current owner to a writer. This parameter is required as an acknowledgement of the side ef"New value: +"[query parameter] Whether to transfer ownership to the specified user and downgrade the current owner to a writer. This parameter is required as an acknowledgement of the side ef"

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`, and if the following additional conditions are met, the requester is granted access: 1. The file "New value: +"[query parameter] Issue the request as a domain administrator. If set to `true`, and if the following additional conditions are met, the requester is granted access: 1. The file "

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "allowFileDiscovery": {
+      "type": "boolean"
+    },
+    "deleted": {
+      "type": "boolean"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "emailAddress": {
+      "type": "string"
+    },
+    "expirationTime": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "inheritedPermissionsDisabled": {
+      "type": "boolean"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "pendingOwner": {
+      "type": "boolean"
+    },
+    "permissionDetails": {
+      "items": {
+        "properties": {
+          "inherited": {
+            "type": "boolean"
+          },
+          "inheritedFrom": {
+            "type": "string"
+          },
+          "permissionType": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "photoLink": {
+      "type": "string"
+    },
+    "role": {
+      "type": "string"
+    },
+    "teamDrivePermissionDetails": {
+      "items": {
+        "properties": {
+          "inherited": {
+            "type": "boolean"
+          },
+          "inheritedFrom": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          },
+          "teamDrivePermissionType": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type": {
+      "type": "string"
+    },
+    "view": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a solid job: it discloses patch semantics, a concurrency warning, readonly refusal, response shape, and request-body handling. It does not cover required authorization scopes or what happens when the permission does not exist, so it is strong but not complete.

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 description is front-loaded with the core action and warning, and most details earn their place for a complex mutation tool. It is somewhat dense and run-on, but not bloated or repetitive.

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?

Given the complexity of a 13-parameter nested mutation with an output schema, the description supplies important missing context: concurrency behavior, readonly refusal, body-passing mechanics, and sibling routing. Authorization requirements and partial failure behavior are not covered, but the definition is broadly complete for invocation guidance.

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 the schema already documents all 13 parameters, including the nested Permission body and query parameters. The description adds useful guidance on passing the body via `params` or `body_file`, but it does not materially clarify the query parameter semantics beyond what the schema provides.

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 uses a specific verb and resource: 'Updates a permission with patch semantics,' and it clearly identifies the target as a Drive permission. It also names the sibling operations (create, delete, get, list), so an agent can distinguish this mutation from adjacent permission tools.

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?

It explains that this is a patch-style update and warns about concurrent modifications, which is useful context for choosing this tool. It also lists sibling operations, but it does not explicitly state when to prefer update over create or give concrete exclusion criteria.

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

Deploy Server