Skip to main content
Glama

clear_range

Destructive

Clears cell values from a range in a Google Sheets spreadsheet. Optionally clears formatting as well.

Instructions

Clear data from a range of cells. Optionally clear formatting too.

Args: spreadsheet_id: The ID of the spreadsheet sheet: Sheet/tab name range: A1 notation range (e.g., 'A1:C10') clear_format: If True, also clears formatting. If False (default), only clears values.

Returns: Result of the clear operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_idYes
sheetYes
rangeYes
clear_formatNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description adds the detail that clearing formatting is optional, which goes beyond the 'destructiveHint' annotation. However, it does not disclose other behavioral traits such as impact on formulas, reversal possibilities, or permission requirements.

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 and front-loaded with the main purpose. The structured 'Args' list presents each parameter efficiently without unnecessary words.

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 low schema coverage and the presence of an output schema, the description adequately covers parameter semantics. However, it lacks context about side effects or comparison with similar tools, which would make it more complete.

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 description coverage, the description fully compensates by providing clear explanations for all four parameters, including examples for 'range' and default behavior for 'clear_format'.

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 'Clear data from a range of cells', specifying the verb 'clear' and the resource 'range of cells'. It distinguishes itself from sibling tools like 'update_cells' or 'delete_rows_columns' by focusing on clearing values within a range.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how it compares to related operations like deleting cells or updating cells.

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/socar-edwin/mcp-google-sheets-extended'

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