grr

Overview Schema Source Related Servers Discussions Admin

drive.comments.get

Retrieve a specific Google Drive comment by file ID and comment ID, using the required fields parameter to return only the comment details you need.

Instructions

Gets a comment by ID. For more information, see Manage comments and replies. Required: The fields parameter must be set. 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: 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.
`commentId`	Yes	[URL path segment] The ID of the comment.
`includeDeleted`	No	[query parameter] Whether to return deleted comments. Deleted comments will not include their original content.	false

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`anchor`	No
`author`	No
`content`	No
`deleted`	No
`replies`	No
`resolved`	No
`createdTime`	No
`htmlContent`	No
`modifiedTime`	No
`quotedFileContent`	No
`assigneeEmailAddress`	No
`mentionedEmailAddresses`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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 return deleted comments. Deleted comments will not include their original content."New value: +"[query parameter] Whether to return deleted comments. Deleted comments will not include their original content."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "anchor": {
+      "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"
+    },
+    "quotedFileContent": {
+      "properties": {
+        "mimeType": {
+          "type": "string"
+        },
+        "value": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "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"
+    },
+    "resolved": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.6/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 usefully states '[HTTP GET]' and that the resource is returned as JSON, which signals a read-only call, but it omits any permission or auth requirements and includes generic body-handling language that is largely irrelevant to a GET endpoint.

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, but the description spends space on documentation links and generic boilerplate about request bodies and `body_file` that is not relevant to a GET request. It is understandable but not tightly focused.

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 the description need not explain return values, and the schema fully documents the parameters. Still, the unsupported `fields` requirement and missing auth/permission context leave an agent with avoidable uncertainty about a correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the parameters, but the description introduces a required `fields` parameter that does not appear in the schema. That is a misleading parameter requirement unless the agent infers it belongs in the `query` array, which the description does not explain.

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 comment by ID.' It also names the sibling operations over the same resource (create, delete, list, update), so an agent can readily distinguish this tool from related comment tools.

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 'by ID' phrasing gives clear context for when to use this tool, and the sibling list helps orient it against alternatives. However, it does not explicitly say when to use get versus list, or explain how to resolve a commentId if unknown.

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

Deploy Server