Skip to main content
Glama

manage_sheet_tabs

Rename, delete, or duplicate a sheet tab in a Google Sheets spreadsheet.

Instructions

Rename, delete, or duplicate a sheet tab inside a spreadsheet.

Single entrypoint for the three most common tab lifecycle operations. To CREATE a new tab from scratch, use create_sheet (separate tool). To reorder tabs, use batch_update with updateSheetProperties.index. Deletion is permanent — the undo is only available through the Sheets UI, not via the API.

Requires OAuth scope: https://www.googleapis.com/auth/spreadsheets (write).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
spreadsheet_idYesGoogle Sheets spreadsheet ID (from the URL after `/d/`).
actionYesWhich operation to perform. One of: - `"rename"` — change the tab's title. Requires `new_name`. - `"delete"` — remove the tab and all its data. Cannot delete the last remaining sheet in a spreadsheet (Google API error). - `"duplicate"` — create a copy of the tab. `new_name` optional (defaults to "Copy of <original>").
sheet_idNoNumeric sheet ID (NOT the spreadsheet ID). Preferred over `sheet_name` because it's unique and stable. Get it from `get_spreadsheet_info` under `sheets[].properties.sheetId`. The first sheet is typically `0`. Either `sheet_id` or `sheet_name` must be provided.
sheet_nameNoTab title (case-sensitive). Used only when `sheet_id` is omitted — the tool looks up the ID by name. Ambiguous if multiple tabs share the name (rare — Sheets UI normally prevents this).
new_nameNoNew title for the tab. Required for `"rename"`. Optional for `"duplicate"` (auto-generated if omitted). Ignored for `"delete"`. Must be unique within the spreadsheet.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses permanent deletion (no API undo) and inability to delete the last remaining sheet. No annotations provided, so description carries full burden. Lacks details on other behaviors like rate limits or auth specifics beyond scope.

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?

Six well-structured sentences with no redundant information. Each sentence adds value: purpose, summary, alternatives, limitations, and scope.

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?

With output schema present and high schema coverage, description covers key aspects. Some minor gaps like error handling but overall complete enough for moderate complexity.

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 83% and already explains parameters well (e.g., action options, sheet_id preference). Description adds minimal extra value beyond schema, so baseline 3 is appropriate.

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?

Description clearly states the tool renames, deletes, or duplicates sheet tabs. It distinguishes from siblings by mentioning 'create_sheet' for new tabs and 'batch_update' for reordering.

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?

Explicitly states when to use (three tab lifecycle operations) and when not to (creating: use create_sheet; reordering: use batch_update). Also notes required OAuth scope.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server