grr

Overview Schema Source Related Servers Discussions Admin

drive.drives.list

Lists a user's shared drives and supports query-based searching, pagination, and domain admin access so you can find and review available shared drives.

Instructions

Lists the user's shared drives. This method accepts the q parameter, which is a search query combining one or more search terms. For more information, see the Search for shared drives guide [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, hide, unhide, update.

Input Schema

Name	Required	Description	Default
`q`	No	[query parameter] Query string for searching shared drives.
`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.
`pageSize`	No	[query parameter] The maximum number of shared drives to return. The service may return fewer than this value. If unspecified, at most 10 shared drives will be returned. The maxi	10
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] Page token for shared drives.
`useDomainAdminAccess`	No	[query parameter] Issue the request as a domain administrator; if set to true, then all shared drives of the domain in which the requester is an administrator are returned.	false

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 26, 2026

addedInput schema / properties / pageSize / default
```
Added value: +"10"
```

changedInput schema / properties / pageSize / description

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

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: -"Page token for shared drives."New value: +"[query parameter] Page token for shared drives."

changedInput schema / properties / q / description

Previous value: -"Query string for searching shared drives."New value: +"[query parameter] Query string for searching shared drives."

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 all shared drives of the domain in which the requester is an administrator are returned."New value: +"[query parameter] Issue the request as a domain administrator; if set to true, then all shared drives of the domain in which the requester is an administrator are returned."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "drives": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "nextPageToken": {
+      "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 carries the burden and does disclose HTTP GET (implying a safe read) and that it returns JSON, which is useful. However it omits auth requirements, rate limits, and any pagination behavior (pageToken/pageSize appear only in schema), and the request-body/body_file boilerplate is largely irrelevant to a GET list call.

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 lead sentence is front-loaded and effective, but a middle sentence about request bodies and `body_file` is boilerplate that does not apply to a GET list operation, adding noise. The sibling listing at the end earns its place; the request-construction text does not.

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?

An output schema exists and schema coverage is complete, so return values and parameter meaning needn't be restated. Still, with zero annotation coverage for an 8-param listing tool, the description could have clarified pagination and read-only safety more explicitly.

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 already documents all eight parameters. The description adds only marginal meaning for `q` ('search query combining one or more search terms') that the schema description largely already conveys. 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?

States a specific verb and resource ('Lists the user's shared drives') and explicitly enumerates the sibling operations over the same resource (create, delete, get, hide, unhide, update), letting an agent distinguish this from them without opening schemas.

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?

The name 'Lists' implies this is the enumeration tool, and naming siblings provides some contrast, but there is no explicit when-to-use/when-not guidance (e.g., list vs get vs teamdrives.list). Usage is inferred rather than stated.

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

Deploy Server