grr

Overview Schema Source Related Servers Discussions Admin

drive.revisions.get

Fetches a specific Google Drive file revision's metadata or content by file ID and revision ID, enabling version inspection or download.

Instructions

Gets a revision's metadata or content by ID. For more information, see Manage file revisions [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: 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.
`revisionId`	Yes	[URL path segment] The ID of the revision.
`acknowledgeAbuse`	No	[query parameter] Whether the user is acknowledging the risk of downloading known malware or other abusive files. This is only applicable when the `alt` parameter is set to `medi	false

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`size`	No
`mimeType`	No
`published`	No
`exportLinks`	No
`keepForever`	No
`md5Checksum`	No
`publishAuto`	No
`modifiedTime`	No
`publishedLink`	No
`originalFilename`	No
`lastModifyingUser`	No
`publishedOutsideDomain`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 26, 2026

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

changedInput schema / properties / acknowledgeAbuse / description

Previous value: -"Whether the user is acknowledging the risk of downloading known malware or other abusive files. This is only applicable when the `alt` parameter is set to `medi"New value: +"[query parameter] Whether the user is acknowledging the risk of downloading known malware or other abusive files. This is only applicable when the `alt` parameter is set to `medi"

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 / revisionId / description

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "exportLinks": {
+      "type": "object"
+    },
+    "id": {
+      "type": "string"
+    },
+    "keepForever": {
+      "type": "boolean"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "lastModifyingUser": {
+      "properties": {
+        "displayName": {
+          "type": "string"
+        },
+        "emailAddress": {
+          "type": "string"
+        },
+        "kind": {
+          "type": "string"
+        },
+        "me": {
+          "type": "boolean"
+        },
+        "permissionId": {
+          "type": "string"
+        },
+        "photoLink": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "md5Checksum": {
+      "type": "string"
+    },
+    "mimeType": {
+      "type": "string"
+    },
+    "modifiedTime": {
+      "type": "string"
+    },
+    "originalFilename": {
+      "type": "string"
+    },
+    "publishAuto": {
+      "type": "boolean"
+    },
+    "published": {
+      "type": "boolean"
+    },
+    "publishedLink": {
+      "type": "string"
+    },
+    "publishedOutsideDomain": {
+      "type": "boolean"
+    },
+    "size": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the HTTP GET method and JSON return, which establishes read-only behavior, but it omits the key operational detail that content retrieval requires the `alt=media` query parameter — that only appears buried in the `acknowledgeAbuse` schema text.

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 purpose is correctly front-loaded in sentence one, but the middle transport paragraph about `body_file` and request-body construction is largely irrelevant for a GET request, and the documentation link plus sibling list add bulk without much signal.

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 all 7 parameters are documented in the schema. However, for a tool whose primary alternate mode is downloading revision content, the absence of any mention of media download semantics or `alt=media` usage leaves a meaningful gap.

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 the baseline is 3. The description restates the precedence rule that typed flags win over the `params` map, but that is already documented in the `params` schema entry, so it adds little beyond the structured fields.

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?

The first sentence gives a specific verb and resource — "Gets a revision's metadata or content by ID" — which is immediately distinguishable from list/delete/update. It names the sibling operations over the same resource but does not explain how they differ, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance. The trailing "Siblings over the same resource: delete, list, update" merely enumerates alternatives without stating the condition that selects this one, and nothing tells the agent how to choose between retrieving metadata versus content.

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

Deploy Server