grr

Overview Schema Source Related Servers Discussions Admin

drive.approvals.list

Lists approvals on a Google Drive file. Specify fields to retrieve approval details, since default responses may omit the items array.

Instructions

Lists the approvals on a file. For more information, see Manage approvals. By default, this method returns a minimal response that may not include the items array. To retrieve approval details, you must explicitly specify the fields you want using the fields query parameter. To return the exact fields you need, see Return specific fields [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: approve, cancel, comment, decline, get, reassign, start.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`fileId`	Yes	[URL path segment] Required. The ID of the file that the approval is on.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`pageSize`	No	[query parameter] The maximum number of approvals to return. When not set, at most 100 approvals are returned.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response.

Output Schema

Name	Required	Description	Default
`kind`	No
`items`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 26, 2026

changedInput schema / properties / fileId / description

Previous value: -"Required. The ID of the file that the approval is on."New value: +"[URL path segment] Required. The ID of the file that the approval is on."

changedInput schema / properties / pageSize / description

Previous value: -"The maximum number of approvals to return. When not set, at most 100 approvals are returned."New value: +"[query parameter] The maximum number of approvals to return. When not set, at most 100 approvals are returned."

addedInput schema / properties / pageSize / format
```
Added value: +"int32"
```

changedInput schema / properties / pageToken / description

Previous value: -"The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response."New value: +"[query parameter] The token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from a previous response."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "approvalId": {
+            "type": "string"
+          },
+          "completeTime": {
+            "type": "string"
+          },
+          "createTime": {
+            "type": "string"
+          },
+          "dueTime": {
+            "type": "string"
+          },
+          "fileContentChangeBehavior": {
+            "enum": [
+              "FILE_CONTENT_CHANGE_BEHAVIOR_UNSPECIFIED",
+              "RESET_APPROVAL",
+              "NO_APPROVAL_ACTION"
+            ],
+            "type": "string"
+          },
+          "initiator": {
+            "properties": {
+              "displayName": {
+                "type": "string"
+              },
+              "emailAddress": {
+                "type": "string"
+              },
+              "kind": {
+                "type": "string"
+              },
+              "me": {
+                "type": "boolean"
+              },
+              "permissionId": {
+                "type": "string"
+              },
+              "photoLink": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "modifyTime": {
+            "type": "string"
+          },
+          "reviewerResponses": {
+            "items": {
+              "properties": {
+                "kind": {
+                  "type": "string"
+                },
+                "response": {
+                  "enum": [
+                    "RESPONSE_UNSPECIFIED",
+                    "NO_RESPONSE",
+                    "APPROVED",
+                    "DECLINED"
+                  ],
+                  "type": "string"
+                },
+                "reviewer": {
+                  "properties": {
+                    "displayName": {
+                      "type": "string"
+                    },
+                    "emailAddress": {
+                      "type": "string"
+                    },
+                    "kind": {
+                      "type": "string"
+                    },
+                    "me": {
+                      "type": "boolean"
+                    },
+                    "permissionId": {
+                      "type": "string"
+                    },
+                    "photoLink": {
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "status": {
+            "enum": [
+              "STATUS_UNSPECIFIED",
+              "IN_PROGRESS",
+              "APPROVED",
+              "CANCELLED",
+              "DECLINED"
+            ],
+            "type": "string"
+          },
+          "targetFileId": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "nextPageToken": {
+      "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?

No annotations are provided, so the description carries the full disclosure burden, and it does surface the most important behavioral trait: a default minimal response that may exclude the items array. It also notes the HTTP GET verb and JSON return. It omits permission/auth requirements and any rate-limit or pagination caveats beyond what the schema already says.

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 and the fields caveat are front-loaded, which is good. But the description pads in two documentation links plus boilerplate about request bodies and body_file ('typed flags win over the `params` map') that is largely irrelevant to a GET list operation, and the trailing sibling list is a bare enumeration.

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 needn't be explained, and the fields caveat covers the main trap. What's missing is permission/auth context for listing approvals on a file and any note on how pageSize/pageToken interact beyond the schema text. Adequate but with clear gaps for a tool with seven parameters.

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 pageSize, pageToken, fileId, and the rest are already fully documented, establishing a baseline of 3. The description adds meaning by introducing the `fields` query parameter, which isn't in the schema at all — useful, but also potentially confusing since it isn't clear whether that goes through the `query` array or elsewhere.

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: 'Lists the approvals on a file.' It also names the sibling actions over the same resource (approve, cancel, comment, decline, get, reassign, start), which lets an agent distinguish listing from acting on an approval. However, those siblings are only listed by name with no explanation of how they differ, so differentiation is implicit rather than explicit.

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?

It gives concrete operational guidance: the default response is minimal and may omit the items array, so the agent must pass explicit `fields` to get details. That's a real usage constraint an agent would otherwise miss. It stops short of stating when to prefer drive.approvals.get over this tool, so it's context-rich but not a full when/when-not guide.

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

Deploy Server