grr

Overview Schema Source Related Servers Discussions Admin

drive.permissions.list

Lists a file's or shared drive's permissions so you can review who has access. Use it to audit sharing settings, then create, update, or delete permissions as needed.

Instructions

Lists a file's or shared drive's permissions. For more information, see Share files, folders, and drives [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: create, delete, get, update.

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.
`pageSize`	No	[query parameter] The maximum number of permissions to return. The service may return fewer than this value. If unspecified, at most 100 permissions will be returned for shared d
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from the previous response.
`supportsAllDrives`	No	[query parameter] Whether the requesting application supports both My Drives and shared drives.	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
`includePermissionsForView`	No	[query parameter] Specifies which additional view's permissions to include in the response. Only `published` is supported.

Output Schema

Name	Required	Description	Default
`kind`	No
`permissions`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 26, 2026

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 / includePermissionsForView / description

Previous value: -"Specifies which additional view's permissions to include in the response. Only `published` is supported."New value: +"[query parameter] Specifies which additional view's permissions to include in the response. Only `published` is supported."

changedInput schema / properties / pageSize / description

Previous value: -"The maximum number of permissions to return. The service may return fewer than this value. If unspecified, at most 100 permissions will be returned for shared d"New value: +"[query parameter] The maximum number of permissions to return. The service may return fewer than this value. If unspecified, at most 100 permissions will be returned for shared d"

addedInput schema / properties / pageSize / format
```
Added value: +"int32"
```
addedInput schema / properties / pageSize / maximum
```
Added value: +100
```
addedInput schema / properties / pageSize / minimum
```
Added value: +1
```

changedInput schema / properties / pageToken / description

Previous value: -"The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from the previous response."New value: +"[query parameter] The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from the previous response."

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 / 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": {
+    "kind": {
+      "type": "string"
+    },
+    "nextPageToken": {
+      "type": "string"
+    },
+    "permissions": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral load. It does disclose the read-only nature via '[HTTP GET]' and states the return is JSON, but it omits permission/scope requirements, pagination behavior, and the fact that shared-drive access depends on supportsAllDrives. The 'request bodies ... read whole from body_file' sentence is boilerplate that is largely inapplicable to a GET list call and adds confusion rather than insight.

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 in the first sentence, which is good, but the remaining text is dominated by generic wrapper boilerplate about request bodies and body_file that is irrelevant for a GET list operation. It is not bloated, but roughly half of it does not earn its place for this specific tool.

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?

With 11 parameters, 100% schema coverage and an output schema present, the description does not need to restate parameters or return values, and it correctly conveys the read semantics and resource scope. The main residual gap is the absence of any hint about shared-drive access requirements given the number of drive-related query flags, but overall it is sufficient to call the tool.

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 explains fileId, pageSize, pageToken, supportsAllDrives and the rest; the baseline is 3. The description does add one piece of real semantics — that typed flags take precedence over the `params` map and that a whole body can come from `body_file` — but that concerns the request-building wrapper, not this endpoint's own parameters.

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 first sentence states a specific verb and resource: listing a file's or shared drive's permissions, which is clearly a read/enumeration operation. It also names the sibling operations over the same resource (create, delete, get, update), so an agent can place it in the CRUD family. It stops short of saying what distinguishes list from get in practice, so it is clear but not maximally differentiating.

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?

Usage is only implied: 'Siblings over the same resource: create, delete, get, update' tells the agent that other operations exist but gives no conditions for choosing list over get, nor any exclusions. There is no statement about when this tool is the right choice versus retrieving a single permission.

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

Deploy Server