Skip to main content
Glama

sheets delete sheet

sheets_delete_sheet
DestructiveIdempotent

Delete a specific tab from a Google Spreadsheet by numeric sheet ID; set confirm=true to authorize the destructive action.

Instructions

Delete a tab (by numeric sheetId) from a spreadsheet. Requires confirm=true.

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_id": "<spreadsheet_id>",
      "sheet_id": "<sheet_id>"
    },
    "name": "sheets_delete_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
sheet_idYes
spreadsheet_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is covered by structured data. The description adds one genuinely new behavioral fact, the confirm=true requirement, but says nothing about whether deleted tab content is recoverable or what happens if the sheetId does not exist. With annotations carrying most of the burden, the added context is real but thin.

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?

Two short sentences with zero filler, and the operation plus its identifier type are front-loaded ahead of the confirm requirement. Every clause carries information an agent needs.

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?

An output schema exists, so return values need not be described, and the annotations cover the destructive and idempotent profile. The description covers the operation, the identifier type, and the confirm gate, missing only recoverability of the deleted tab and behavior on an invalid sheetId.

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 compensate for three bare-named parameters. It explains sheet_id as a numeric identifier and clarifies that confirm must be true, but leaves spreadsheet_id wholly unexplained and does not note that confirm defaults to false in the schema while the description implies it is mandatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Delete a tab ... from a spreadsheet') and disambiguates the identifier as a numeric sheetId rather than a name. It does not explicitly contrast with siblings such as sheets_clear_range, which removes contents without deleting the tab, so an agent must infer that distinction from the names alone.

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 prerequisite 'Requires confirm=true' is stated, which is the main gate an agent must satisfy before calling. However, there is no guidance on when to delete a tab versus clearing it, and no mention that the calling default for confirm is false, so a call without setting it will fail.

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