grr

Overview Schema Source Related Servers Discussions Admin

drive.teamdrives.get

Fetches a Team Drive resource by ID and returns it as JSON; deprecated, use drives.get instead.

Instructions

Deprecated: Use drives.get 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, list, update.

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.
`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.
`teamDriveId`	Yes	[URL path segment] The ID of the Team Drive
`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 T	false

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`name`	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.

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / teamDriveId / description

Previous value: -"The ID of the Team Drive"New value: +"[URL path segment] The ID of the Team 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 T"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 T"

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

First observedOct 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses deprecation status and the GET/read nature of the call, but says nothing about authorization requirements, domain-admin behavior, or what a failure looks like.

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 and immediately actionable. However, the middle sentence about request bodies and `body_file` is irrelevant for an HTTP GET that sends no body, so real estate is spent on content that cannot apply here.

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?

For a deprecated read with an output schema and fully described parameters, the essentials are nearly covered: what it is, that it is being replaced, and how parameters are assembled. What is missing is a one-clause statement of what a Team Drive resource is being fetched by ID, which would let an agent decide without cross-referencing the schema.

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 all six parameters are already documented in the schema, and the 3 baseline applies. The description adds one piece of meaning the schema doesn't state directly — that typed parameters override the `params` map and that `body_file` replaces parameter-built bodies — but this is generic wrapper boilerplate rather than insight specific to this endpoint.

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?

Names the operation (HTTP GET, returns the requested resource as JSON) and lists the sibling operations (create, delete, list, update) so an agent can locate it within the teamdrives family. The concrete resource type ('Team Drive') is left to the tool name and the `teamDriveId` schema field rather than stated outright, which keeps it short of a 5.

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?

Opens with an explicit 'Deprecated: Use `drives.get` instead', which is a direct alternative-naming instruction an agent can act on without inference. It does not explain what the replacement does or when this call might still be needed, so it stops short of full when/when-not coverage.

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

Deploy Server