Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

Clear Spreadsheet Values

sheets_clear_values
DestructiveIdempotent

Clear cell values from a range in a Google Spreadsheet while keeping formatting intact. Provide spreadsheet ID and range to remove content.

Instructions

Clear cell values from a specific range in a Google Spreadsheet (keeps formatting).

Args:

  • spreadsheet_id (string): The ID of the Google Spreadsheet

  • range (string): The A1 notation range to clear (e.g., 'Sheet1!A1:D10')

Returns: { "spreadsheetId": string, "clearedRange": string }

Examples:

  • Clear range: range="Sheet1!A1:D10"

  • Clear entire sheet: range="Sheet1"

Input Schema

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

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

Annotations indicate destructive and idempotent behavior. The description adds 'keeps formatting', which is a key behavioral nuance not captured by annotations. It also describes the return value.

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 concise: one sentence for the purpose, structured Args/Returns/Examples sections. Every part adds value without redundancy.

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?

Given the schema richness and annotations, the description covers what the tool does, its parameters, return value, and examples. It is complete enough for a clear operation, though it could mention error handling or prerequisites.

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%, but the description adds value by providing examples of how to use the range parameter (including clearing an entire sheet) and clarifying the purpose of each parameter.

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 the action ('clear cell values'), the resource ('Google Spreadsheet'), and a key differentiator ('keeps formatting'). This distinguishes it from tools like sheets_update_values or sheets_delete_range.

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 implies usage for clearing values without affecting formatting, but does not explicitly state when to use this tool versus alternatives or when not to use it.

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