Skip to main content
Glama
Sign In
Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

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

by taylorwilsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Manage Sheet Tab

manage_sheet_tab
Destructive

Manages an existing sheet tab by renaming, deleting, hiding, unhiding, reordering, or styling it with tab color and gridline settings. Use it to control the tab itself rather than its rows or columns.

Instructions

Manages an existing sheet tab: rename, delete, hide, unhide, reorder, or style (tab color and gridlines).

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

NameRequiredDescriptionDefault
actionYesOne of "rename", "delete", "hide", "unhide", "reorder", "style"
new_nameNoNew title, required for action="rename"
new_indexNoNew zero-based position, required for action="reorder"
tab_colorNoFor action="style": hex tab color (#RRGGBB), or "none" to remove it
sheet_nameYesTitle of the existing tab to act on
show_gridlinesNoFor action="style": show (True) or hide (False) the sheet's gridlines
spreadsheet_idYesID of the spreadsheet
user_google_emailYesUser's Google email address

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.0
    • changedInput schema / properties / action / description
      Previous value: -"One of \"rename\", \"delete\", \"hide\", \"unhide\", \"reorder\""New value: +"One of \"rename\", \"delete\", \"hide\", \"unhide\", \"reorder\", \"style\""
    • addedInput schema / properties / show_gridlines
      Added value: +{
+  "default": null,
+  "description": "For action=\"style\": show (True) or hide (False) the\nsheet's gridlines",
+  "type": "boolean"
+}
    • addedInput schema / properties / tab_color
      Added value: +{
+  "default": null,
+  "description": "For action=\"style\": hex tab color (#RRGGBB), or \"none\" to\nremove it",
+  "type": "string"
+}
  2. Changed4 schema fields changedv1.28.0
    • 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"
  3. Addedv1.26.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is structured. The description adds scope by saying it operates on the tab itself, but it does not explain what delete destroys, whether actions are reversible, or what permissions are required.

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 two sentences, front-loaded with the core operation list and followed by focused sibling disambiguation. Every sentence carries useful routing or scope information.

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?

Given the rich input schema, output schema, and annotations, the description is mostly complete for selecting and invoking the tool. The main remaining gap is action-specific behavioral detail around destructive deletes and permission constraints.

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%, and the schema already documents the action enum and conditional requirements such as new_name for rename and new_index for reorder. The description names the actions but does not add parameter-level semantics beyond the schema.

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 states a specific resource (an existing sheet tab) and enumerates the supported operations: rename, delete, hide, unhide, reorder, and style. It clearly distinguishes this tool from create_sheet and resize_sheet_dimensions.

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?

It explicitly routes the agent to create_sheet for adding tabs and resize_sheet_dimensions for row/column changes, while clarifying that this tool operates on the tab itself. It lacks only edge-case exclusions, such as when specific actions may be invalid.

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