Skip to main content
Glama
Sign In
MCP Google Sheets

MCP Google Sheets

by toantran201
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete Rows

delete_rows

Permanently removes a specified range of rows from a sheet tab, moving lower rows up. Specify the starting row and number of rows to delete.

Instructions

Permanently deletes a contiguous block of rows from a sheet tab, shifting the rows below upward. Deletes count rows (default 1) starting at the 1-based start_row. Destructive — cannot be undone via the API.

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": "<spreadsheet>",
      "sheet_name": "<sheet_name>",
      "start_row": "<start_row>"
    },
    "name": "delete_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of consecutive rows to delete, starting at start_row (default 1)
start_rowYes1-based index of the first row to delete
sheet_nameYesTarget sheet tab name
spreadsheetYesTarget spreadsheet: a full Google Sheets URL (https://docs.google.com/spreadsheets/d/<ID>/edit...) or a bare spreadsheet ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: it explicitly states the operation is destructive and cannot be undone via the API, and describes the shifting effect. This provides comprehensive transparency.

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 two sentences with no fluff. It front-loads the main action and effect, then adds specifics and a critical warning. Every sentence is necessary and well-structured.

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?

The description covers the tool's purpose, behavior, and destructive nature. However, it omits information about the return value (no output schema exists). For a tool with four parameters, the description is largely complete but lacks this detail.

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 coverage is 100%, so the baseline is 3. The description reinforces the count default and 1-based start_row but does not add significant meaning beyond what the schema's property descriptions already provide.

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 specifies that the tool permanently deletes a contiguous block of rows from a sheet tab, shifting rows upward. It uses specific verbs and resources ('deletes rows') and distinguishes from siblings by focusing on row deletion, unlike add_rows or update_row.

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 provides clear context (permanent deletion, shifting rows) but does not explicitly state when not to use this tool or suggest alternatives. It implies usage for removing rows, meeting the criteria for 'clear context, no exclusions'.

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

Deploy Server

Other Tools