Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

List Document Comments

drive_list_comments
Read-onlyIdempotent

List comments from a Google Doc, supporting pagination, deleted comments, and output in Markdown or JSON format.

Instructions

List comments on a Google Doc.

Args:

  • file_id (string): The ID of the Google Doc

  • include_deleted (boolean): Include deleted comments (default: false)

  • page_size (number): Max comments to return, 1-100 (default: 20)

  • page_token (string, optional): Pagination token for next page

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON format: { "comments": [ { "id": string, "content": string, "author": string, "createdTime": string, "resolved": boolean, "quotedFileContent": string, "replies": [{ "id", "content", "author", "createdTime" }] } ], "next_page_token": string | null }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idYesThe ID of the Google Doc to list comments from
include_deletedNoWhether to include deleted comments
page_sizeNoMaximum number of comments to return (1-100)
page_tokenNoToken for pagination to retrieve the next page of results
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds context about pagination and output format but does not discuss rate limits or other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with args and returns sections, front-loading the purpose. It is slightly verbose but remains efficient and clear.

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 5 parameters, full schema coverage, and annotations, the description is thorough. It explains the return format and pagination, compensating for the lack of an output schema.

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% with descriptions for all parameters. The description adds value by listing default values and providing the return format structure, which is not in the schema.

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 clearly states 'List comments on a Google Doc' with a specific verb and resource. It distinguishes itself from sibling tools like drive_create_comment and drive_delete_comment.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. Usage is implied by the tool's name and sibling context, but no exclusions or conditions are stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EveryInc/google-workspace-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server