gdocs-mcp

Resolve or reopen a comment

resolve_comment

Resolve or reopen a Google Docs comment thread by ID, verifying the quoted text first to prevent resolving the wrong thread.

Instructions

Resolve (or reopen) a comment thread by comment id. expectQuotedText is REQUIRED: the quotedText list_comments gave for that comment, exactly. It is checked against the live comment first, so a stale or wrong id is refused instead of resolving the wrong thread.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "commentId": "<commentId>",
      "expectQuotedText": "<expectQuotedText>"
    },
    "name": "resolve_comment"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	The doc: a Drive id or URL, or /folder/doc. A tab path names its doc.
`reopen`	No	reopen instead of resolve
`account`	No	Google account email to use. Defaults to GDOCS_DEFAULT_ACCOUNT, or the sole account.
`commentId`	Yes
`expectQuotedText`	Yes	the comment’s quotedText from list_comments; verified before the comment is changed

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.0Oct 31, 2026

removedInput schema / properties / documentId
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / expectQuote

Removed value: -{
-  "description": "snippet of the comment’s quoted text/body; verified before resolving",
-  "type": "string"
-}

addedInput schema / properties / expectQuotedText

Added value: +{
+  "description": "the comment’s quotedText from list_comments; verified before the comment is changed",
+  "type": "string"
+}

addedInput schema / properties / path

Added value: +{
+  "description": "The doc: a Drive id or URL, or /folder/doc. A tab path names its doc.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "documentId",
-  "commentId"
-]New value: +[
+  "path",
+  "commentId",
+  "expectQuotedText"
+]

First observedv0.1.1Aug 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: expectQuotedText is verified against the live comment before mutation, so a stale id is refused rather than resolving the wrong thread. That is genuinely valuable safety context. Remaining gaps, such as required permissions or the shape of the follow-up read, keep it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and the required-parameter rule; every clause carries usable information and nothing is repeated from the title.

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 no output schema, the description covers the main correctness risk (wrong thread resolved via stale id) and points to the sibling that produces the required value. It leaves permissions and any returned confirmation unstated, which is a minor but real gap.

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 80%, so most parameters are already documented, but commentId has no schema description and the description supplies its origin (the commentId from list_comments) along with the contract for expectQuotedText. It clarifies why the verification parameter exists and what happens when it fails, adding meaning beyond the schema text rather than restating it.

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 ('Resolve (or reopen) a comment thread by comment id'), immediately distinguishing it from the read-only siblings list_comments and add_comment. The title and first sentence together let an agent place it precisely in the comment workflow.

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 description routes the agent to list_comments as the source of the required `quotedText`, which is a concrete usage precondition rather than vague context. It doesn't cover access prerequisites or when a resolve should be skipped in favor of add_comment, so it stops short of naming exclusions explicitly.

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