Skip to main content
Glama
Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Manage Document Comment

manage_document_comment
Destructive

Create, reply to, resolve, edit, or delete comments on Google Docs to coordinate document feedback and keep review discussions organized.

Instructions

Manage comments on a Google Document.

Actions:

  • create: Create a new document-level comment. Requires comment_content. Note: The Drive API cannot anchor comments to specific text; only the Google Docs UI can do that.

  • reply: Reply to a comment. Requires comment_id and comment_content.

  • resolve: Resolve a comment. Requires comment_id.

  • update: Edit a comment's text. Requires comment_id and comment_content.

  • delete: Delete a comment. Requires comment_id.

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": {
      "user_google_email": "<user_google_email>",
      "document_id": "<document_id>",
      "action": "<action>"
    },
    "name": "manage_document_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
comment_idNo
document_idYes
comment_contentNo
user_google_emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.28.0
    • removedInput schema / properties / comment_content / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / comment_content / type
      Added value: +"string"
    • removedInput schema / properties / comment_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / comment_id / type
      Added value: +"string"
  2. Addedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already flag this as destructive, non-idempotent, and open-world, so the safety profile is covered by structured data. The description adds one genuinely useful behavioral fact — that the Drive API cannot anchor comments to specific text — but says nothing about whether delete is permanent, what permissions are needed, or how resolve/update affect existing replies.

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?

A one-line scope statement followed by a scannable per-action bullet list, with required inputs inline and the anchoring caveat folded into the action it affects. No sentence is redundant and the structure is front-loaded.

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?

Given an output schema exists and annotations cover the mutation risk, the description is largely complete: every action and its inputs are documented. The remaining gap is behavior on destructive paths (permanence of delete, effect of resolve on future replies) plus auth expectations.

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 description coverage is 0% and the action parameter has no enum, so the description carries real weight: it supplies the five legal action values and maps comment_id/comment_content to the branches that require them. It leaves user_google_email and document_id unexplained, though both are self-describing required fields.

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 description names a specific resource (comments on a Google Document) and enumerates five concrete operations (create, reply, resolve, update, delete), so an agent knows exactly what surface this tool covers. It does not explicitly distinguish itself from the sibling list_document_comments (read path), leaving that inference to the name alone.

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?

Each action is paired with its required inputs, which implies when each branch applies (e.g., reply needs comment_id plus content). However, there is no guidance on when to use this tool versus list_document_comments to read existing threads, and no stated preconditions or exclusions.

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

Deploy Server

Other Tools