grr

Overview Schema Source Related Servers Discussions Admin

drive.permissions.get

Retrieves a Google Drive permission by file ID and permission ID, returning sharing details as JSON for access audits or sharing checks.

Instructions

Gets a permission by ID. For more information, see Share files, folders, and 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, list, update.

Input Schema

Name	Required	Description	Default
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`fileId`	Yes	[URL path segment] The ID of the file.
`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.
`permissionId`	Yes	[URL path segment] The ID of the permission.
`supportsAllDrives`	No	[query parameter] Whether the requesting application supports both My Drives and shared drives.	false
`supportsTeamDrives`	No	[query parameter] Deprecated: Use `supportsAllDrives` instead.	false
`useDomainAdminAccess`	No	[query parameter] Issue the request as a domain administrator. If set to `true`, and if the following additional conditions are met, the requester is granted access: 1. The file	false

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`role`	No
`type`	No
`view`	No
`domain`	No
`deleted`	No
`photoLink`	No
`displayName`	No
`emailAddress`	No
`pendingOwner`	No
`expirationTime`	No
`permissionDetails`	No
`allowFileDiscovery`	No
`teamDrivePermissionDetails`	No
`inheritedPermissionsDisabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 26, 2026

changedInput schema / properties / fileId / description

Previous value: -"The ID of the file."New value: +"[URL path segment] The ID of the file."

changedInput schema / properties / permissionId / description

Previous value: -"The ID of the permission."New value: +"[URL path segment] The ID of the permission."

addedInput schema / properties / supportsAllDrives / default
```
Added value: +"false"
```

changedInput schema / properties / supportsAllDrives / description

Previous value: -"Whether the requesting application supports both My Drives and shared drives."New value: +"[query parameter] Whether the requesting application supports both My Drives and shared drives."

addedInput schema / properties / supportsTeamDrives / default
```
Added value: +"false"
```

changedInput schema / properties / supportsTeamDrives / description

Previous value: -"Deprecated: Use `supportsAllDrives` instead."New value: +"[query parameter] Deprecated: Use `supportsAllDrives` instead."

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`, and if the following additional conditions are met, the requester is granted access: 1. The file "New value: +"[query parameter] Issue the request as a domain administrator. If set to `true`, and if the following additional conditions are met, the requester is granted access: 1. The file "

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "allowFileDiscovery": {
+      "type": "boolean"
+    },
+    "deleted": {
+      "type": "boolean"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "domain": {
+      "type": "string"
+    },
+    "emailAddress": {
+      "type": "string"
+    },
+    "expirationTime": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "inheritedPermissionsDisabled": {
+      "type": "boolean"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "pendingOwner": {
+      "type": "boolean"
+    },
+    "permissionDetails": {
+      "items": {
+        "properties": {
+          "inherited": {
+            "type": "boolean"
+          },
+          "inheritedFrom": {
+            "type": "string"
+          },
+          "permissionType": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "photoLink": {
+      "type": "string"
+    },
+    "role": {
+      "type": "string"
+    },
+    "teamDrivePermissionDetails": {
+      "items": {
+        "properties": {
+          "inherited": {
+            "type": "boolean"
+          },
+          "inheritedFrom": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          },
+          "teamDrivePermissionType": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type": {
+      "type": "string"
+    },
+    "view": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses HTTP GET and that the response is JSON, which establishes the basic read-only behavior. However, it does not mention auth/scopes, shared-drive access implications, or error behavior, and the generic body_file sentence is odd boilerplate for a GET.

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 first sentence is front-loaded and useful. The middle sentence about request bodies and body_file is largely irrelevant boilerplate for a GET endpoint, which weakens conciseness and could confuse an agent about whether a request body is expected.

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?

The tool has an output schema and full schema coverage, so return values and parameters are documented elsewhere. The description supplies purpose, HTTP method, and sibling context, which is sufficient for correct invocation. Missing auth or permission prerequisites keeps it from being fully complete.

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 schema already documents all parameters. The description adds only generic wrapper guidance about typed parameters winning over the params map and body_file usage, without adding meaning for fileId, permissionId, or the query flags. 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?

The description states a specific verb and resource: "Gets a permission by ID." It also names the sibling operations over the same resource (create, delete, list, update), so an agent can distinguish retrieval-by-ID from those alternatives without inspecting schemas.

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 sibling list gives clear context that this is the retrieval-by-ID operation, with list as the related alternative for multiple permissions. It does not explicitly state when-not to use it or any prerequisites, so it falls short of the top score.

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

Deploy Server