google-workspace-mcp-server

Delete Comment

drive_delete_comment

DestructiveIdempotent

Delete a specific comment from a Google Doc using its file and comment IDs. This action permanently removes the comment.

Instructions

Delete a comment from a Google Doc.

Args:

file_id (string): The ID of the Google Doc
comment_id (string): The ID of the comment to delete

Returns: { "deleted": true, "comment_id": string }

Note: This action cannot be undone.

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": {
      "file_id": "<file_id>",
      "comment_id": "<comment_id>"
    },
    "name": "drive_delete_comment"
  }
}

Input Schema

Name	Required	Description	Default
`file_id`	Yes	The ID of the Google Doc containing the comment
`comment_id`	Yes	The ID of the comment to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.3May 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds the explicit warning 'This action cannot be undone,' which reinforces the destructive nature and provides additional context beyond the structured annotations. It does not explain idempotency behavior, but the existing annotation covers that.

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 description is well-structured with a clear first line, an Args section, a Returns section, and a warning note. Every sentence earns its place, and it is appropriately sized—neither overlong nor cryptic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the purpose, parameters, return value shape, and irreversibility warning. Given the tool's simplicity and strong annotations, this is sufficient for an agent to select and invoke it correctly. No output schema exists, so the Returns example compensates well.

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

Parameters3/5

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

The input schema provides 100% coverage with clear descriptions for both file_id and comment_id. The description's Args section repeats the schema info without adding new meaning. Per the rubric, baseline for high schema coverage is 3, and no extra value is added here.

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 'Delete a comment from a Google Doc' uses a specific verb and resource, clearly differentiating it from sibling comment tools like create, reply, resolve, and list. It is unambiguous and action-oriented.

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?

Usage is implied by the verb 'delete' and the resource, but no explicit guidance is provided about when to prefer this tool over alternatives. There is no mention of preconditions or exclusions, though the 'cannot be undone' note offers a hint about appropriate caution.

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