grr

Overview Schema Source Related Servers Discussions Admin

drive.comments.update

Modify an existing Google Drive comment using patch semantics. Set fields to return only needed data, or dry-run to preview the request before sending.

Instructions

Updates a comment with patch semantics. 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 PATCH] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON Comment object accepting anchor, assigneeEmailAddress, author, content, createdTime, deleted, htmlContent, id and 6 more fields; pass it via params or whole via body_file Siblings over the same resource: create, delete, get, list.

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] 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. The body is a JSON Comment object.
`commentId`	Yes	[URL path segment] The ID of the comment.
`request_body`	No	Request body of type Comment: pass it via `params` (merged into the built body) or whole via `body_file`.

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.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON Comment object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type Comment: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "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"
+}

Changed3 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."

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

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses PATCH (partial-update) semantics, states it is refused under --readonly safety profiles (i.e., this is a write), and notes the response is the API resource as JSON. It omits auth/permission requirements (who may edit a comment) and what happens to fields not supplied, which keeps it short of a 5.

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?

Purpose is front-loaded, which is right, but the single run-on paragraph is cluttered with documentation links, bracketed asides, and an explanation of the return value that duplicates the existing output schema. Those sentences do not all earn their place.

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?

For a mutation tool with no annotations and a nested request body, it covers the essentials an agent needs to call it: required `fields`, body shape and delivery path, safety-profile behavior, and sibling navigation. Missing permission/auth context is the main residual gap; return values are already covered by the output schema.

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

Parameters4/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, but the description adds real value: it flags that `fields` is mandatory — a parameter absent from the schema properties — and explains that the request body is a Comment object passed either via `params` or whole via `body_file`. The 'id and 6 more fields' enumeration is vague filler, but the routing guidance is genuinely beyond the schema.

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?

States a specific verb and resource ('Updates a comment') plus the update style ('patch semantics'), and closes by naming the four siblings over the same resource (create, delete, get, list), so an agent can separate it from read/create/delete calls without opening any schema.

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 a hard precondition — the `fields` parameter must be set — and enumerates the sibling tools on the same resource, which frames the alternatives. What it lacks is an explicit 'use this when you want to change content/resolve a comment, not when…' conditional, so guidance is implied rather than stated.

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

Deploy Server