grr

Overview Schema Source Related Servers Discussions Admin

drive.drives.unhide

Restore a hidden shared drive to its default view via the Google Drive API, with dry-run previews available and request blocked under read-only safety profiles.

Instructions

Restores a shared drive to the default view. For more information, see Manage shared drives [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response 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, list, update.

Input Schema

Name	Required	Description
`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.

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.

Changed2 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."

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.7/5.0

Behavior4/5

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

With no annotations, the description carries the disclosure burden and does reasonably well: it flags HTTP POST, that it mutates state, and that it is refused under --readonly safety profiles. It also explains request-body construction and that a JSON response resource is returned. It omits reversibility/permission scope, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence and the sibling list closes it out cleanly. The generic body-building and response-format clauses are somewhat boilerplate-heavy, but no sentence is truly wasted.

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?

An output schema exists, so return values needn't be detailed, and the mutation/safety behavior is covered. What's missing is the permission requirement and a concrete definition of what 'default view' means for the drive's hidden state.

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 baselines apply. The description's note that typed flags win over the `params` map and that bodies can come from `body_file` largely restates what the schema already documents for those same fields, adding little new meaning for driveId.

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?

States a specific verb and resource: restores a shared drive to the default view (the inverse of hide). It also enumerates the sibling operations on the same resource, so an agent can place it in the drive lifecycle. It doesn't explicitly say 'this is the inverse of hide', leaving that inference to the reader.

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: the readonly-refusal note tells the agent it will fail under read-only safety profiles, which is a useful gating condition. But there is no direct statement of when to call unhide versus hide/update, nor of required permissions (e.g. organizer role).

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

Deploy Server