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 Spreadsheet Comment

manage_spreadsheet_comment
Destructive

Create, reply to, resolve, update, or delete comments on a Google Spreadsheet, including cell-anchored and file-level comments.

Instructions

Manage comments on a Google Spreadsheet.

Actions:

  • create: Create a new comment. Requires comment_content. Pass cell (A1 notation, e.g. 'Sheet1!B2'; defaults to the first sheet) to anchor it to a cell; otherwise it is a file-level comment.

  • 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>",
      "spreadsheet_id": "<spreadsheet_id>",
      "action": "<action>"
    },
    "name": "manage_spreadsheet_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
cellNo
actionYes
comment_idNo
spreadsheet_idYes
comment_contentNo
user_google_emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / properties / cell
      Added value: +{
      +  "default": null,
      +  "type": "string"
      +}
  2. 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"
  3. Addedv1.0.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the risk profile is covered structurally. The description adds useful behavioral detail — a comment with no cell becomes a file-level comment, and cell defaults to the first sheet — but says nothing about irreversibility of delete, effect of resolve on reply threads, or auth/permission needs.

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?

The purpose sentence is front-loaded and the five actions are presented as a scannable bullet list with the required parameter inline for each. Every line carries operational information; there is no filler or repetition.

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?

With six parameters, an action enum, and an output schema already present, the description covers nearly everything an agent needs to invoke it correctly. Remaining gaps are minor: no statement of permission requirements and no clarification of how resolve interacts with existing replies.

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%, so the description carries the burden, and it mostly does: it defines the meaning of action values, ties comment_id and comment_content to specific actions, and explains cell's A1 notation format and its first-sheet default. Only spreadsheet_id and user_google_email are left unexplained, and both are largely self-evident.

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 Spreadsheet') and enumerates five concrete operations (create, reply, resolve, update, delete), so an agent knows exactly what capability is offered. It does not explicitly differentiate itself from siblings such as list_spreadsheet_comments or manage_document_comment, leaving that inference to the reader.

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?

Per-action prerequisites are spelled out ('create requires comment_content', 'resolve requires comment_id'), which effectively tells the agent which action to pick and what it must supply. What is missing is routing guidance against alternatives (e.g., reading comments belongs to list_spreadsheet_comments) and any preconditions such as permission requirements.

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