grr

Overview Schema Source Related Servers Discussions Admin

drive.replies.list

Lists replies to a specific comment on a Google Drive file, supporting pagination and optional inclusion of deleted replies.

Instructions

Lists a comment's replies. For more information, see Manage comments and replies [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, get, 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.
`pageSize`	No	[query parameter] The maximum number of replies to return. The service may return fewer than this value. If unspecified, at most 20 replies will be returned. The maximum value is	20
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`commentId`	Yes	[URL path segment] The ID of the comment.
`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 the previous response.
`includeDeleted`	No	[query parameter] Whether to include deleted replies. Deleted replies don't include their original content.	false

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 26, 2026

changedInput schema / properties / commentId / description

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

changedInput schema / properties / fileId / description

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

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

changedInput schema / properties / includeDeleted / description

Previous value: -"Whether to include deleted replies. Deleted replies don't include their original content."New value: +"[query parameter] Whether to include deleted replies. Deleted replies don't include their original content."

addedInput schema / properties / pageSize / default
```
Added value: +"20"
```

changedInput schema / properties / pageSize / description

Previous value: -"The maximum number of replies to return. The service may return fewer than this value. If unspecified, at most 20 replies will be returned. The maximum value is"New value: +"[query parameter] The maximum number of replies to return. The service may return fewer than this value. If unspecified, at most 20 replies will be returned. The maximum value is"

addedInput schema / properties / pageSize / format
```
Added value: +"int32"
```
addedInput schema / properties / pageSize / maximum
```
Added value: +100
```
addedInput schema / properties / pageSize / minimum
```
Added value: +1
```

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 the 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 the previous response."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "kind": {
+      "type": "string"
+    },
+    "nextPageToken": {
+      "type": "string"
+    },
+    "replies": {
+      "items": {
+        "properties": {
+          "action": {
+            "type": "string"
+          },
+          "assigneeEmailAddress": {
+            "type": "string"
+          },
+          "author": {
+            "properties": {
+              "displayName": {
+                "type": "string"
+              },
+              "emailAddress": {
+                "type": "string"
+              },
+              "kind": {
+                "type": "string"
+              },
+              "me": {
+                "type": "boolean"
+              },
+              "permissionId": {
+                "type": "string"
+              },
+              "photoLink": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "content": {
+            "type": "string"
+          },
+          "createdTime": {
+            "type": "string"
+          },
+          "deleted": {
+            "type": "boolean"
+          },
+          "htmlContent": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "mentionedEmailAddresses": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "modifiedTime": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does convey read-only behavior via '[HTTP GET]' and says the response is JSON, but the body_file/params paragraph describes request-body construction that is irrelevant to a GET and adds noise and potential confusion. It says nothing about pagination behavior, permission requirements, or whether deleted replies require a flag.

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 front-loaded well and the doc link is compact, but the middle paragraph on request bodies and body_file is boilerplate that does not apply to a read-only list call. The trailing sibling enumeration is terse but only partially useful.

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?

Contextual needs are modest: an output schema exists and the 100%-covered schema documents the pagination and filtering parameters, so the description needn't restate them. However, it omits any mention that replies are paginated or that includeDeleted affects returned content, and its transport boilerplate is mismatched to a GET operation.

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%, with fileId, commentId, pageSize, pageToken, and includeDeleted all documented in the schema itself. The description adds no parameter-level meaning of its own, so the baseline of 3 applies.

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 names a specific verb and resource ('Lists a comment's replies'), which unambiguously identifies the operation. The sibling line ('create, delete, get, update') confirms this is the enumeration variant over the replies resource, though it stops short of contrasting against the adjacent drive.comments.list.

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?

Use is implied by the verb 'list' and by naming the sibling mutations, but there is no explicit statement of when to reach for this tool versus drive.comments.list or drive.replies.get. The link to the Manage comments guide offers some context, though it is generic rather than decision-oriented.

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

Deploy Server