Skip to main content
Glama

sheets_delete_rows

Delete one or more rows from a Google Sheet by specifying a full-row A1 range.

Instructions

Delete one or more rows from a Google Sheet using a full-row A1 range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeYesFull-row A1 range to delete (e.g., "Sheet1!2:4" or "Sheet1!3:3"). If sheet name is omitted, the first sheet is used
spreadsheetIdYesThe ID of the spreadsheet (found in the URL after /d/)
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It states 'Delete' but does not mention side effects like shifting of subsequent rows, permanence, or error conditions. This is insufficient for a destructive operation.

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?

A single, well-structured sentence that front-loads the purpose and method. No wasted words.

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

Completeness3/5

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

Given no output schema and low complexity (2 params, flat), the description is partially adequate but missing important context like return value, error handling, or prerequisites for deletion. Additional completeness would improve safety.

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% with good descriptions for both parameters. The description adds value by clarifying the 'full-row A1 range' format and noting that omitting sheet name defaults to the first sheet, which goes beyond the schema's example.

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 ('Delete'), the resource ('one or more rows from a Google Sheet'), and the method ('using a full-row A1 range'), which is specific and distinguishes from sibling tools like sheets_delete_columns or sheets_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?

The description lacks any guidance on when to use this tool versus alternatives (e.g., sheets_clear_values to clear data without deleting rows, or sheets_delete_sheet to remove an entire sheet). No when-not or context for selection is provided.

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/freema/mcp-gsheets'

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