Skip to main content
Glama
shakhin85

Google Sheets MCP Server

by shakhin85

clear_range

Clear data from a specific range of cells in a Google Sheet using A1 notation.

Instructions

Clear values from a range of cells

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeYesThe A1 notation range to clear (e.g., 'Sheet1!A1:D10')
spreadsheet_idYesThe ID of the spreadsheet
Behavior2/5

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

With no annotations, the description must carry the full burden. It only states 'Clear values' but does not disclose whether formatting, comments, or other cell data are affected, nor does it address destructive behavior or side effects. This lack of detail is insufficient.

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 a single, short sentence that is concise and directly states the tool's purpose. It is appropriately sized and front-loaded, but could include slightly more detail without becoming verbose.

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

Completeness2/5

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

For a mutation tool with no output schema and no annotations, the description is too minimal. It does not explain return values (e.g., what is cleared, any confirmation) or the scope of the clear operation (values only vs. entire cell contents). This leaves gaps for the agent.

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?

Both parameters are fully described in the input schema (100% coverage). The description adds no additional meaning or constraints beyond what the schema provides, so a baseline score of 3 is appropriate.

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 'Clear values from a range of cells' clearly specifies the action (clear) and the resource (range of cells), distinguishing it from sibling tools like read_range, write_range, and delete_sheet.

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?

No guidance is provided on when to use this tool versus alternatives like delete_sheet or batch_update. There is no mention of prerequisites, such as requiring the spreadsheet to be writable, or exclusions like not affecting formatting.

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/shakhin85/google-sheets-mcp-server'

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