ai-toolkit

add_sheet_tab

Add a new worksheet to a Google Spreadsheet. Creates an empty tab so you can then write data into it via range updates, which is otherwise impossible for non-existent tabs.

Instructions

Add a new tab (worksheet) to a spreadsheet.

Creates an empty worksheet — the structural edit update_sheet_range and friends can't do, since they only touch cells within tabs that already exist. After adding, write into it with update_sheet_range using "<title>!A1" as the range.

sheet_id is the spreadsheet's ID (the long token in its URL, .../spreadsheets/d/<sheet_id>/edit) and is required. title is the new tab's name; it must not collide with an existing tab (see list_sheet_tabs). index optionally sets the tab's 0-based position in the tab strip (0 puts it first); omit to append it at the end. Returns a summary including the new tab's numeric sheetId.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`index`	No
`title`	Yes
`sheet_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A4.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it explains that a new empty worksheet is created, that sheet_id is required, title must be unique, index controls position, and the return includes the numeric sheetId. It stops short of discussing permissions or failure modes, but covers the core behavioral contract thoroughly.

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 yet information-dense, front-loading the core purpose before parameter details. Every sentence earns its place and there is no filler or repetition.

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?

For a 3-parameter tool with no annotations and an output schema, the description fully covers purpose, all parameters, constraints, return summary, and relationships to sibling tools. An agent has everything needed to call it correctly and integrate it with adjacent operations.

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

Parameters5/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 explain every parameter. It does: sheet_id's URL format and requirement, title's uniqueness constraint with a pointer to list_sheet_tabs, and index's 0-based positioning with default append behavior. This adds substantial meaning beyond the raw 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 uses a specific verb ('Add') and resource ('tab/worksheet') and clearly distinguishes it from cell-level operations like update_sheet_range. It states exactly what the tool creates and even contrasts it with what sibling tools cannot do.

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?

It explicitly names alternatives and complementary follow-up steps: update_sheet_range cannot create tabs, so use this tool first and then write with update_sheet_range using a tab-qualified range. It also tells the agent to consult list_sheet_tabs to avoid title collisions, making usage conditions explicit.

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