google-workspace-mcp-server

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"

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

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes	The ID of the Google Spreadsheet
`range`	Yes	The A1 notation range to clear (e.g., 'Sheet1!A1:D10')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.3May 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate destructive and non-read-only behavior. The description adds valuable context: it preserves formatting, shows the return object, and includes examples like clearing an entire sheet with a sheet name. This goes beyond the annotation hints.

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, well-structured (purpose, args, returns, examples), and front-loaded with the main action. Every sentence has purpose and no filler.

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 simple two-parameter tool with strong annotations and schema coverage, the description is complete. It explains behavior, provides return fields, and covers edge cases with examples. No output schema is needed because returns are described in the description.

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?

Input schema covers 100% of parameters with descriptions. The description reinforces these but also adds an example that clarifies the range parameter accepts a sheet name alone for entire-sheet clearing, which is not explicit 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 the tool's purpose: 'Clear cell values from a specific range in a Google Spreadsheet (keeps formatting).' This uses a specific verb-action and resource, and the formatting note distinguishes it from sibling tools like sheets_update_values or sheets_append_values.

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

Usage Guidelines4/5

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

The description implies when to use the tool (clearing values while preserving formatting) but does not explicitly mention alternatives or exclusions. The context is clear enough for an agent to differentiate, but no explicit 'use this instead of X' guidance is given.

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