google-workspace-mcp

sheets_add_sheet

Add a new sheet or tab to a specified Google Sheets spreadsheet using the spreadsheet's unique ID and the new tab's title.

Instructions

Add a new sheet/tab to a spreadsheet.

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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "title": "<title>"
    },
    "name": "sheets_add_sheet"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`spreadsheet_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the basic effect and omits context such as required permissions, position of the new sheet, behavior on duplicate titles, or any side effects.

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 a single, well-structured sentence that is front-loaded with the action and resource. It is appropriately concise with no wasted words.

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 simple add operation, the description and schema are minimally adequate, but the description lacks usage context, alternative clarifications, and behavioral details. The presence of an output schema helps, but the lack of any guidance on when to use it or what happens on conflict makes it incomplete.

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% and the description does not mention parameter names, formats, or meanings. The phrase 'to a spreadsheet' vaguely implies spreadsheet_id and 'new sheet/tab' implies title, but the description does not add meaningful detail beyond the schema field names.

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 clearly states the action ('Add'), the resource ('a new sheet/tab'), and the target ('to a spreadsheet'). This distinguishes it from sibling tools like sheets_create (which creates a spreadsheet) and sheets_delete_sheet (which removes a sheet).

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. Sibling tools like sheets_duplicate_sheet and sheets_create exist, but the description does not clarify how this tool fits.

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

Deploy Server