Skip to main content
Glama
Sign In
google-sheets-mcp

google-sheets-mcp

by AurelioCecchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete a tab

delete_tab

Permanently removes a spreadsheet tab and all its contents; requires confirm=true, so use it only after explicit user approval.

Instructions

Permanently deletes a tab and all its contents. Not reversible from this server: the only recovery is Google Sheets' version history. Requires confirm=true, and explicit user confirmation should be obtained before calling it.

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>",
      "title": "<title>",
      "confirm": "<confirm>"
    },
    "name": "delete_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesExact name of the tab to delete.
confirmYesMust be true. Exists to make deletion a deliberate act.
spreadsheetIdYesSpreadsheet ID, or its full URL. The ID is the segment between /d/ and /edit in the URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well: states permanence, the recovery path (version history), and the confirm=true requirement. These are exactly the behavioral traits an agent needs to avoid accidental data loss.

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?

Three tight sentences: action + permanence, recovery constraint, and confirmation requirement. Front-loaded with the destructive nature; every clause earns its place.

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

Completeness5/5

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

For a destructive no-annotation tool with no output schema, the description covers what matters: irreversibility, recovery path, and confirmation gating. Nothing essential for safe invocation is missing.

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% with rich per-parameter descriptions (title, confirm, spreadsheetId URL parsing), so the schema already documents parameters thoroughly. The description adds the confirm requirement contextually but doesn't exceed what the schema provides.

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?

States a specific verb and resource: permanently deletes a tab and all its contents. This clearly distinguishes it from siblings like clear_range (which empties without deleting) and add_tab/rename_tab.

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?

Explains it is not reversible except via version history, and that explicit user confirmation should be obtained before calling. It implies when to use (intentional removal of entire tabs) but doesn't contrast with clear_range explicitly; that gap is minor given the destructive nature is front-loaded.

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