google-workspace-mcp-server

Duplicate Sheet

sheets_duplicate_sheet

Duplicate a sheet within a Google Spreadsheet by specifying the spreadsheet ID and sheet ID. Optionally, name the new sheet copy.

Instructions

Duplicate a sheet within the same spreadsheet.

Args:

spreadsheet_id (string): The ID of the Google Spreadsheet
sheet_id (number): The ID of the sheet to duplicate (use sheets_get_spreadsheet to find sheet IDs)
new_sheet_name (string, optional): Name for the new sheet (defaults to 'Copy of [original name]')

Returns: { "sheetId": number, "title": string, "index": number }

Examples:

Duplicate sheet: spreadsheet_id="...", sheet_id=0
Duplicate with new name: spreadsheet_id="...", sheet_id=0, new_sheet_name="January Data"

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_id": "<sheet_id>"
    },
    "name": "sheets_duplicate_sheet"
  }
}

Input Schema

Name	Required	Description
`spreadsheet_id`	Yes	The ID of the Google Spreadsheet
`sheet_id`	Yes	The ID of the sheet to duplicate (use sheets_get_spreadsheet to find sheet IDs)
`new_sheet_name`	No	Name for the new sheet (defaults to 'Copy of [original name]')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.3May 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already communicate that this is a non-read-only, non-destructive write operation. The description adds helpful behavioral detail such as the default name for the new sheet and the structure of the returned object, without contradicting the annotations.

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 well-structured with clear Args, Returns, and Examples sections. Every sentence adds value, and the one-sentence purpose is direct and sufficient.

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 simple tool with two required parameters, no output schema, and strong annotations, the description provides enough context: examples, default behavior, output shape, and a pointer to a related tool. It is complete without being over-engineered.

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?

The input schema descriptions cover all three parameters at 100%, including the default-name behavior and the hint to use sheets_get_spreadsheet. The description repeats these details rather than adding new semantic information, so the baseline score of 3 is appropriate.

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 the specific verb 'Duplicate' with the resource 'a sheet within the same spreadsheet', making the tool's exact scope clear. This distinguishes it from sibling tools such as sheets_create_spreadsheet and drive_copy_file.

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?

The description clearly establishes when to use the tool (duplicating a sheet inside the same spreadsheet) and even directs users to sheets_get_spreadsheet for finding sheet IDs. It lacks an explicit 'when not to use' or direct alternative comparison, but the context is unambiguous.

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