Google Workspace (GWS) MCP Server

drive_replies_get

Read-only

Retrieve a specific reply to a comment in Google Drive by providing file, comment, and reply IDs. Use this to fetch reply details or include deleted replies.

Instructions

Get a single reply to a comment.

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": {
      "fileId": "<fileId>",
      "commentId": "<commentId>",
      "replyId": "<replyId>"
    },
    "name": "drive_replies_get"
  }
}

Input Schema

Name	Required	Description
`fields`	No	Fields to include (e.g. "id,content,action")
`fileId`	Yes	The file the comment belongs to
`replyId`	Yes	The reply to retrieve
`commentId`	Yes	The parent comment
`includeDeleted`	No	Whether to return the reply if it has been deleted (it will have no content)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.1Sep 24, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already communicates that this is a safe, non-mutating operation, and the description aligns with that. However, the description itself adds little behavioral context beyond the schema, such as deleted-reply behavior or response characteristics.

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, compact sentence that gets straight to the point with no filler. It is front-loaded with the core verb and resource, making it easy for an agent to parse quickly.

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 simple read operation, the description, schema, and readOnlyHint annotation cover the essential invocation context: required IDs are in the schema and safety is in the annotations. It does not explain the return value, but that gap is minor for a standard getter.

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?

Schema description coverage is 100%, so all five parameters are already documented in the input schema. The tool description adds no additional parameter meaning, so the baseline score of 3 applies.

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 a specific verb ('Get'), a resource ('a single reply'), and a scope ('to a comment'), which clearly identifies what the tool does. This also distinguishes it from drive_replies_list by focusing on a single reply rather than all replies.

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 explicit guidance on when to use this tool versus alternatives such as drive_replies_list, drive_replies_create, or drive_replies_update. The word 'single' implies a distinction from listing, but no when-to-use or when-not-to-use context is provided.

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

Deploy Server