mcp-google-sheets

get_comments

Read-only

Retrieve comments from a Google Sheet with details like author, content, anchor cell, and resolved status. Optionally include resolved comments or limit the number returned.

Instructions

Get all comments on a spreadsheet.

Args: spreadsheet_id: The ID of the spreadsheet include_resolved: Whether to include resolved comments (default False) max_results: Maximum number of comments to return (default 50)

Returns: List of comments with author, content, anchor cell, and resolved status

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": {
      "spreadsheet_id": "<spreadsheet_id>"
    },
    "name": "get_comments"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes
`include_resolved`	No
`max_results`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true; description adds value by explaining return format (list with author, content, anchor cell, resolved status) and default parameter values (include_resolved=False, max_results=50).

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?

One-sentence purpose followed by concise parameter list. No wasted words; front-loaded with action and resource.

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?

For a read-only list tool with output schema present, description adequately covers purpose, parameters, and return format. No gaps given the context.

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

Parameters5/5

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

With 0% schema coverage, description fully explains all three parameters: spreadsheet_id (required), include_resolved (boolean, default False), max_results (integer, default 50). Adds meaning beyond schema titles and types.

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?

Description clearly states 'Get all comments on a spreadsheet.' with specific verb and resource, distinguishing it from sibling tools like add_comment and resolve_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?

No explicit guidance on when to use this tool versus alternatives; the agent must infer from the name and context. Lacks when-not-to-use or alternative tool mentions.

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