Skip to main content
Glama
Hermoso

Hermoso

Official

Add, rename or delete a sheet tab

manage_sheet_tabs
Destructive

Add, rename, or delete a tab in a Google Spreadsheet, with delete guarded by a filled-cell count confirmation and the last remaining tab protected from removal.

Instructions

Add, rename or delete a tab in a Google Spreadsheet. action:"add" + title · action:"rename" + tab + newTitle · action:"delete" + tab. Name the tab by its TITLE or its numeric sheetId (list_sheet_tabs gives both); an unknown tab is refused with the real list rather than a Google error nobody can map back. DELETING a tab destroys everything on it: call it without confirm first to get the filled-cell count, then confirm:true + confirmCells. Google does not allow removing the LAST remaining tab in a file, and that is refused by name with the way out (clear it, or delete the whole file with delete_drive_file). Every action is read back from the spreadsheet before it is reported as done.

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": {
      "action": "<action>"
    },
    "name": "manage_sheet_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNowhich tab — its title or numeric sheetId (rename / delete)
titleNothe name for the new tab (action:"add")
actionYesadd, rename or delete a tab
confirmNotrue deletes a tab that holds data; needs confirmCells
newTitleNowhat to rename the tab to (action:"rename")
sheetUrlNoGoogle Sheets link, instead of spreadsheetId
confirmCellsNothe filled-cell count an unconfirmed delete reported
spreadsheetIdNoGoogle spreadsheet id; use this or sheetUrl

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.465
    • addedInput schema / properties / action / description
      Added value: +"add, rename or delete a tab"
    • addedInput schema / properties / confirm / description
      Added value: +"true deletes a tab that holds data; needs confirmCells"
    • addedInput schema / properties / confirmCells / description
      Added value: +"the filled-cell count an unconfirmed delete reported"
    • addedInput schema / properties / sheetUrl / description
      Added value: +"Google Sheets link, instead of spreadsheetId"
    • addedInput schema / properties / spreadsheetId / description
      Added value: +"Google spreadsheet id; use this or sheetUrl"
  2. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes well beyond: it says exactly what is destroyed ('DELETING a tab destroys everything on it'), mandates the unconfirmed-call-then-confirm:true+confirmCells handshake with the filled-cell count as the token, and discloses that Google refuses deleting the last tab and that refusal is surfaced by name with a way out. The read-back verification promise closes the loop on whether the operation actually took effect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action verbs and their parameter maps, then escalates to the destructive path and the last-tab edge case. The compact mid-dot notation ('action:"add" + title · ...') is efficient, though the single dense block is slightly harder to scan than separated lines.

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?

With 8 parameters, no output schema and a destructive annotation, the description carries the full burden and does so: it covers input mapping, the confirmation gate, the platform-level failure mode, refusal messaging, and post-action verification. Nothing material an agent needs to call this safely is missing.

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%, so the baseline is 3, but the description adds relational meaning the schema does not: which parameters pair with which action, that 'tab' accepts either a title or a numeric sheetId, and that confirmCells must be the count a prior unconfirmed delete reported. Only mild remaining gap is that it never mentions sheetUrl/spreadsheetId alternates in prose.

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?

Opens with a specific verb set and resource: 'Add, rename or delete a tab in a Google Spreadsheet.' It then enumerates the three actions so the agent knows exactly which operations are in scope, and the sibling list_sheet_tabs is explicitly named later as the discovery counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit parameter recipe per action (action:"add" + title, action:"rename" + tab + newTitle, action:"delete" + tab), states the two-step protocol for destructive deletes, and names concrete alternatives/escape hatches (clear it, or delete_drive_file). No inference is required to pick the right path.

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