mcp-google-sheets-server

sheets_delete_columns

Deletes a range of columns from a specified Google Sheets spreadsheet and sheet, using start and end column indices.

Instructions

Delete columns from a specific position

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": {
      "spreadsheetId": "<spreadsheetId>",
      "sheetId": "<sheetId>",
      "startIndex": "<startIndex>"
    },
    "name": "sheets_delete_columns"
  }
}

Input Schema

Name	Required	Description
`sheetId`	Yes	The ID of the sheet
`endIndex`	No	Ending column index (0-based)
`startIndex`	Yes	Starting column index (0-based)
`spreadsheetId`	Yes	The ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description only says 'Delete columns', which implies destructiveness but does not mention irreversibility, side effects on formulas or references, or permission requirements. The lack of detail leaves the agent uncertain about the full impact.

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, concise sentence that directly states the action and target. It avoids unnecessary detail or redundant wording, making it efficient and easy to parse.

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?

The description is adequate for a straightforward delete operation but omits important context such as whether the endIndex is inclusive or exclusive, and the fact that deleting columns will shift subsequent columns. Given the simplicity of the operation, a score of 3 is appropriate.

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?

The input schema already provides descriptions for all parameters, including the 0-based indexing of startIndex and endIndex. The tool description adds no extra semantic information beyond what is already in the schema, so it meets the baseline but does not enhance understanding.

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 uses the specific verb 'Delete' and identifies the resource 'columns' in a spreadsheet, distinguishing it from sibling tools like delete_rows or delete_sheet. The phrase 'from a specific position' further clarifies the operation's scope.

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?

No explicit guidance is given about when to use this tool instead of alternatives. However, the operation is self-explanatory and clearly intended for removing columns, so the context is implied but not explicitly stated.

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