Skip to main content
Glama
Sign In
google-docs-mcp

google-docs-mcp

by dbuxton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

docs_delete_comment

Remove a specific comment from a Google Doc by providing the document ID and comment ID.

Instructions

Delete a comment from a Google Doc.

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": {
      "doc_id": "<doc_id>",
      "comment_id": "<comment_id>"
    },
    "name": "docs_delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesGoogle Doc ID
comment_idYesID of the comment to delete

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior on its own. It only says 'delete,' which signals destructiveness, but it does not state whether deletion is permanent, whether replies are also deleted, or what permissions/side effects are involved.

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 a single concise sentence that front-loads the action and object with no filler or repetition. It is easily parsed by an agent.

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

Completeness3/5

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

For a two-parameter tool with a present output schema, the call itself is well specified. However, because this is a destructive operation with no annotations, the description should have included at least a note on permanence or side effects to be fully contextually complete.

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 schema already documents both required parameters (doc_id and comment_id) at 100% coverage, so the description does not need to repeat them. It also adds no extra meaning beyond what the schema gives.

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 states the exact operation (delete), the resource (a comment), and the container (a Google Doc). It is immediately distinguishable from siblings such as docs_add_comment, docs_reply_to_comment, and docs_resolve_comment because those do not delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to delete versus resolving a comment, and no mention of alternatives or prerequisites such as permissions. An agent cannot infer when this tool should be preferred over docs_resolve_comment or docs_read_comments.

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