grr

Overview Schema Source Related Servers Discussions Admin

drive.drives.get

Retrieve a shared drive's metadata by ID, optionally issuing the request as a domain administrator. Returns the resource as JSON.

Instructions

Gets a shared drive's metadata by ID. For more information, see Manage shared 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, hide, list, unhide, 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.
`driveId`	Yes	[URL path segment] The ID of the shared drive.
`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.
`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 s	false

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`name`	No
`hidden`	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 / driveId / description

Previous value: -"The ID of the shared drive."New value: +"[URL path segment] The ID of the shared 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 s"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 s"

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

First observedOct 26, 2026

TDQS

A3.6/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 burden. It does disclose the transport ([HTTP GET]) and that the resource is returned as JSON, but says nothing about access requirements (shared drive membership, or the domain-admin path implied by useDomainAdminAccess) or failure behavior. The request-body/params boilerplate is largely irrelevant for a read operation.

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 core purpose is front-loaded in the first sentence, but the definition is padded with a documentation link, an HTTP-method tag, and a request-body construction clause that does not apply to a metadata read.

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?

For a simple read-by-ID with a fully described schema and an output schema covering return values, the description covers what the tool does and how it relates to its siblings. The remaining gap is access/permission context, which is not stated.

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 baseline is 3. The description's mention that typed flags win over the params map and that body_file can supply a whole body merely restates schema text and has little bearing on a GET request.

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 ('Gets a shared drive's metadata by ID') and explicitly names the sibling operations over the same resource (create, delete, hide, list, unhide, update), so an agent can distinguish it from drive.drives.list without opening either schema.

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 'by ID' phrasing implies this is the lookup-by-identifier path versus the enumeration path, and siblings are listed, but there is no explicit when-to-use/when-not or statement that list should be used when the ID is unknown. Usage is inferable 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