Skip to main content
Glama

sheets_duplicate_sheet

Idempotent

Duplicate a sheet in Google Sheets using its spreadsheet and sheet IDs, with options to name the copy and set its position.

Instructions

Duplicate a sheet within a Google Sheets spreadsheet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetIdYesThe ID of the sheet to duplicate (use sheets_get_metadata to find sheet IDs)
newSheetNameNoThe name for the duplicated sheet
spreadsheetIdYesThe ID of the spreadsheet (found in the URL after /d/)
insertSheetIndexNoThe index where the new sheet should be inserted (0-based)
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds minimal context beyond that: it states the operation is within the same spreadsheet, which is useful but does not clarify behavior like whether the original is preserved or what happens with existing data. No contradiction with annotations is present.

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, direct sentence with no filler or redundancy. It immediately conveys the core purpose and is easy to parse.

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?

The description and schema cover the basic operation and parameters, but there is no output schema and no mention of edge cases (e.g., default new sheet name if not provided, behavior when the sheet name already exists). Given the tool's simplicity and annotation coverage, this is adequate but not rich.

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 provides 100% coverage of parameters, each with its own description. The tool description adds no additional parameter context, but since the schema already fully documents the parameters, a 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 clearly states the action (duplicate), the resource (a sheet), and the context (within a Google Sheets spreadsheet). It is specific and distinct from sibling tools like 'sheets_insert_sheet' (creates an empty sheet) and 'sheets_copy_to' (copies to another spreadsheet).

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

Usage Guidelines3/5

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

The description implies usage (when you want to duplicate a sheet) but does not provide explicit guidance on when to choose this over alternatives, nor does it mention any prerequisites or exclusions. Sibling tools such as sheets_insert_sheet and sheets_copy_to exist, but no comparative guidance is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/freema/mcp-gsheets'

If you have feedback or need assistance with the MCP directory API, please join our Discord server