Skip to main content
Glama

delete_range

Delete a range of cells in a Google Sheet and shift the remaining cells up or left to fill the gap.

Instructions

Delete cells in an A1 range, shifting remaining cells by ROWS or COLUMNS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeYes
spreadsheet_idYes
shift_dimensionNoROWS
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the deletion and shift behavior but omits side effects (e.g., formatting, data validation, irreversibility), prerequisites (e.g., sheet existence, permissions), and error conditions. For a destructive operation, more behavioral context is needed.

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 a single sentence that is front-loaded with the verb and object, followed by the key behavioral detail. Every word adds value; no fluff or repetition.

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 tool's simplicity (no output schema, few params), the description covers the essential behavior for correct invocation. It explains the range type, the shift dimension, and the action. It lacks details on error handling or return values, but these are less critical for a straightforward operation.

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?

Schema description coverage is 0%, so the description must add meaning. It explains shift_dimension by mentioning 'ROWS or COLUMNS', clarifying its valid values. For 'range', it adds 'A1' notation context. However, 'spreadsheet_id' remains unexplained. Overall, it partially compensates for the missing schema descriptions.

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 verb 'delete', the resource 'cells in an A1 range', and the behavioral detail 'shifting remaining cells by ROWS or COLUMNS'. This distinguishes it from siblings like clear_range (no shift) and delete_rows/delete_columns (remove entire rows/columns, not 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 Guidelines3/5

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

The description implies the tool is used when you want to delete a range and shift cells, but it does not explicitly state when to avoid it (e.g., use clear_range to clear without shifting, or delete_rows to remove entire rows). Given the large number of siblings, explicit 'when to use' and 'when not to use' would improve clarity.

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

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