Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Manage Sheet Tab

manage_sheet_tab

Destructive

Rename, delete, hide, unhide, or reorder a sheet tab to control the structure and visibility of a Google spreadsheet.

Instructions

Manages the lifecycle of an existing sheet tab: rename, delete, hide, unhide or reorder.

Use create_sheet to add a tab, and resize_sheet_dimensions for row and column level changes. This tool operates on the tab itself.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	One of "rename", "delete", "hide", "unhide", "reorder"
`new_name`	No	New title, required for action="rename"
`new_index`	No	New zero-based position, required for action="reorder"
`sheet_name`	Yes	Title of the existing tab to act on
`spreadsheet_id`	Yes	ID of the spreadsheet
`user_google_email`	Yes	User's Google email address

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / new_index / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / new_index / type
```
Added value: +"integer"
```
- removedInput schema / properties / new_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / new_name / type
```
Added value: +"string"
```
Addedv1.26.0Sep 6, 2026

TDQS

A4.3/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=false, covering the safety profile. The description adds the 'operates on the tab itself' scoping and lists the operations, but it does not go further to explain consequences such as whether deleting is permanent or whether renaming affects references. It is adequate but not rich beyond the annotations.

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 compact and front-loaded: it states the purpose and operations in the first sentence, then routes to sibling tools in the second. There is no wasted text or repetition of schema details.

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 a 100%-covered schema, annotations, and an output schema available, the description is sufficient for correct invocation. It clearly identifies the operation set and sibling boundaries; nothing needed for selecting or calling the tool 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 description coverage is 100%, so the schema already explains every parameter including action-specific requirements like new_name for 'rename' and new_index for 'reorder'. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 names a specific verb ('manage') and resource ('existing sheet tab'), and enumerates the exact operations: rename, delete, hide, unhide, reorder. It also distinguishes itself from sibling tools by explicitly stating it operates on the tab itself rather than creating tabs or resizing rows/columns.

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?

The description provides explicit routing guidance: use create_sheet for adding a tab, use resize_sheet_dimensions for row/column changes, and use this tool for tab-level lifecycle operations. It clearly sets boundaries between this tool and the most closely related alternatives.

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

Deploy Server