grr

Overview Schema Source Related Servers Discussions Admin

drive.teamdrives.list

Lists Team Drives with search, pagination, and domain-admin access; deprecated, so use drives.list for the same request.

Instructions

Deprecated: Use drives.list instead [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
`q`	No	[query parameter] Query string for searching Team 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] Maximum number of Team Drives to return.	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 Team Drives.
`useDomainAdminAccess`	No	[query parameter] Issue the request as a domain administrator; if set to true, then all Team Drives of the domain in which the requester is an administrator are returned.	false

Output Schema

Name	Required	Description	Default
`kind`	No
`teamDrives`	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: -"Maximum number of Team Drives to return."New value: +"[query parameter] Maximum number of Team Drives to return."

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

changedInput schema / properties / q / description

Previous value: -"Query string for searching Team Drives."New value: +"[query parameter] Query string for searching Team 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 Team 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 Team Drives of the domain in which the requester is an administrator are returned."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "kind": {
+      "type": "string"
+    },
+    "nextPageToken": {
+      "type": "string"
+    },
+    "teamDrives": {
+      "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"
+              },
+              "canChangeSharingFoldersRequiresOrganizerPermissionRestriction": {
+                "type": "boolean"
+              },
+              "canChangeTeamDriveBackground": {
+                "type": "boolean"
+              },
+              "canChangeTeamMembersOnlyRestriction": {
+                "type": "boolean"
+              },
+              "canComment": {
+                "type": "boolean"
+              },
+              "canCopy": {
+                "type": "boolean"
+              },
+              "canDeleteChildren": {
+                "type": "boolean"
+              },
+              "canDeleteTeamDrive": {
+                "type": "boolean"
+              },
+              "canDownload": {
+                "type": "boolean"
+              },
+              "canEdit": {
+                "type": "boolean"
+              },
+              "canListChildren": {
+                "type": "boolean"
+              },
+              "canManageMembers": {
+                "type": "boolean"
+              },
+              "canReadRevisions": {
+                "type": "boolean"
+              },
+              "canRemoveChildren": {
+                "type": "boolean"
+              },
+              "canRename": {
+                "type": "boolean"
+              },
+              "canRenameTeamDrive": {
+                "type": "boolean"
+              },
+              "canResetTeamDriveRestrictions": {
+                "type": "boolean"
+              },
+              "canShare": {
+                "type": "boolean"
+              },
+              "canTrashChildren": {
+                "type": "boolean"
+              }
+            },
+            "type": "object"
+          },
+          "colorRgb": {
+            "type": "string"
+          },
+          "createdTime": {
+            "type": "string"
+          },
+          "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"
+              },
+              "sharingFoldersRequiresOrganizerPermission": {
+                "type": "boolean"
+              },
+              "teamMembersOnly": {
+                "type": "boolean"
+              }
+            },
+            "type": "object"
+          },
+          "themeId": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it does disclose the HTTP method (GET) and JSON response, which signals a safe read. However, most of the text is generic request-construction boilerplate about body building and `body_file`, which is irrelevant (and mildly confusing) for a GET listing operation, and it says nothing about pagination, permission scope, or domain-admin behavior effects.

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 deprecation warning is correctly front-loaded, which is the single most important fact. But the middle clause about request bodies and `body_file` is dead weight for a read-only listing call and dilutes the actionable guidance.

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, so return values need not be explained, and the deprecation pointer covers the main decision an agent must make. Still, a deprecated eight-parameter listing call with no annotations would benefit from a note on pagination and on whether the legacy endpoint still returns results, neither of which is present.

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 each of the eight parameters (q, pageSize, pageToken, useDomainAdminAccess, etc.) is already documented in the schema, making 3 the baseline. The description adds no per-parameter meaning; its only cross-parameter remark — typed flags win over the `params` map — merely restates what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with the deprecation and the replacement (`drives.list`), which implies the resource being enumerated, and it names the immediate siblings (create, delete, get, update). But the actual verb-noun statement of what this call does is replaced by generic boilerplate ("Returns the requested resource as JSON"), so an agent learns it is a legacy list-like call mostly from the tool name rather than the description.

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?

The very first token is an explicit exclusion: "Deprecated: Use `drives.list` instead," naming the exact alternative an agent should pick. It never states the conditions under which, if any, this legacy variant should still be invoked, which keeps it from a 5.

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

Deploy Server