Skip to main content
Glama
Sign In
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

by conorbronsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

drive_replies_create

Post replies to Google Drive file comments, and resolve or reopen threads by setting the action. Combine reply text with resolve/reopen to leave closing notes.

Instructions

Add a reply to a comment, or resolve/reopen it — a comment can only be resolved or reopened by posting a reply with action set. content is required unless action is set; combine both to leave closing/reopening text. Setting action changes the parent comment's resolved field, but resolving is advisory only: the API keeps accepting further replies and doesn't hide anything itself, it's on the client to act on resolved being true (e.g. hide or dim the thread).

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>"
    },
    "name": "drive_replies_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoSet to change the parent comment's resolved state instead of (or alongside) replying with text
fieldsNoFields to include (e.g. "id,content,action")
fileIdYesThe file the comment belongs to
contentNoReply text. Required if action is not set
commentIdYesThe comment to reply to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical runtime behavior: resolving is advisory only, the API continues accepting replies, and the client must act on resolved=true. This is exactly the kind of non-obvious side effect that annotations like readOnlyHint=false do not convey.

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?

Three sentences, all information-dense and front-loaded with the core purpose. The follow-up sentences explain the content/action relationship and the advisory resolution behavior without any filler or repetition of the schema.

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?

Given the absence of an output schema, the description still covers everything needed to invoke the tool correctly: required parameters are implied, the action/content interplay is explained, and the unusual advisory-only resolution behavior is disclosed. No significant invocation-relevant context is missing.

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 coverage is 100%, so the baseline is 3, but the description adds relational semantics: content is required unless action is set, both can be combined, and action mutates the parent comment's resolved field. This clarifies how the parameters interact beyond their individual schema descriptions.

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 opens with a specific action and resource: 'Add a reply to a comment, or resolve/reopen it.' It clearly differentiates the tool from comment-level operations by stating that resolution/reopening is only done through posting a reply with an action set.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool versus alternatives: 'a comment can only be resolved or reopened by posting a reply with action set.' It also gives the content/action precondition, telling the agent exactly when content is required and when action suffices.

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