Skip to main content
Glama

sheets add sheet

sheets_add_sheet

Add a new tab to an existing Google Sheets spreadsheet so agents can create dedicated sheets for data, reports, or workflows.

Instructions

Add a new tab to an existing 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>",
      "sheet_title": "<sheet_title>"
    },
    "name": "sheets_add_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheet_titleYes
spreadsheet_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutation profile is covered structurally. The description adds nothing beyond that: it does not say what happens on a duplicate tab name, whether the new tab is appended at a particular position, or what the response contains, despite having an output schema to point at.

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 ten-word sentence with the action and target front-loaded and no filler. It is efficient, though the brevity reflects under-specification rather than disciplined trimming.

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

Completeness2/5

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

The tool is simple (two required parameters, output schema present), but a mutation tool with no annotation-level detail about failure modes needs the description to cover title-collision behavior and permission requirements. Those gaps are unaddressed, leaving it thin for even a straightforward write operation.

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 carries the full burden of explaining the two parameters. It only weakly maps them via the words 'tab' and 'existing spreadsheet'; it never states that sheet_title is the new tab's display name or that spreadsheet_id must reference an existing file, nor any format expectations.

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 states a specific verb and resource ('Add a new tab to an existing spreadsheet'), which is enough for an agent to distinguish it from a read or delete operation. It stops short of naming its closest sibling, sheets_delete_sheet, so the contrast with alternatives is left implicit.

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 reach for this tool versus siblings such as sheets_create_spreadsheet or sheets_delete_sheet, and no prerequisites (e.g., write access, the spreadsheet needing to exist) are stated. The only usage signal is the implicit 'existing spreadsheet' constraint.

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