Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_manage_tab

Destructive

Add, rename, duplicate, or delete tabs in Google Sheets to organize spreadsheet content and restructure workbooks.

Instructions

Add, rename, duplicate or delete a tab.

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": {
      "spreadsheetId": "<spreadsheetId>",
      "action": "<action>",
      "tab": "<tab>"
    },
    "name": "sheets_manage_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabYes
actionYes
newNameNo
spreadsheetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered structurally. However, the description adds nothing beyond the verb list: it never states that delete removes the tab and its contents irreversibly, that duplicate copies contents, or what happens on name collisions — context an agent needs before invoking a destructive mutation.

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?

A single front-loaded sentence with zero filler that maps cleanly onto the action enum. Its brevity is efficient, though it borders on under-specification given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter destructive mutation with no output schema and no documented parameters, the description is thinner than the tool's complexity warrants. It covers the operation set but omits the conditional parameter requirements and destructive consequences an agent must know before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 carry parameter meaning, and it does not. It never says that newName is required for rename/duplicate and ignored otherwise, or what form the tab identifier takes — leaving all four parameters undocumented in both schema and prose.

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?

The description gives a concrete resource (tab) and enumerates the four supported operations (add, rename, duplicate, delete), matching the action enum exactly. It is clear what the tool does, though it does not differentiate itself from siblings like sheets_batch_update or sheets_format.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over alternatives, nor any exclusions or prerequisites (e.g., permissions needed to delete a tab). Usage can only be inferred from the verb list, and the agent gets no help routing between this and the batch/format siblings.

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