Skip to main content
Glama
tg-tool

Google Sheets Write MCP Server

by tg-tool

duplicate_sheet

Duplicate an existing sheet within the same Google spreadsheet. Specify the source sheet name and new title to create a copy at an optional position.

Instructions

Duplicate a sheet within the same spreadsheet.

Whitelist note: allowed only when writable_sheets is "*" or the new title is explicitly listed.

Args: spreadsheet_id_or_url: Full Sheets URL or bare spreadsheet ID. sheet: Source sheet name OR gid string. new_title: Name for the copy. insert_index: Optional 0-based tab position for the copy. dry_run: If true, return the execution plan without changing anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetYes
dry_runNo
new_titleYes
insert_indexNo
spreadsheet_id_or_urlYes
Behavior4/5

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

No annotations are provided, so the description must convey behavioral information. It explains the dry_run parameter for safe execution and notes the whitelist constraint. However, it does not specify exactly what is duplicated (e.g., data, formatting, formulas) or potential side effects, leaving some ambiguity.

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 concise and well-structured: a one-line purpose, a brief whitelist note, and a clear parameter list. Every sentence adds value with no wasted words.

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

Completeness4/5

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

Given the tool has 5 parameters, no output schema, and no annotations, the description covers purpose, permissions, and parameter details adequately. However, it could be more complete by mentioning what happens to the copied content (e.g., duplicates entire sheet including data and formatting) but is still sufficient for an agent.

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?

With 0% schema description coverage, the description fully explains each parameter: 'spreadsheet_id_or_url: Full Sheets URL or bare spreadsheet ID', 'sheet: Source sheet name OR gid string', 'new_title: Name for the copy', 'insert_index: Optional 0-based tab position', and 'dry_run: If true, return the execution plan'. This adds significant meaning beyond the 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 clearly states 'Duplicate a sheet within the same spreadsheet.' This is a specific verb (duplicate) and resource (sheet), and it distinguishes from sibling tools like add_sheet, delete_sheet, and rename_sheet by indicating it creates a copy.

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 includes a whitelist note that provides permission context: 'allowed only when writable_sheets is "*" or the new title is explicitly listed.' This is a clear usage guideline. However, it does not explicitly mention when to use this tool versus alternatives like copying content manually.

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/tg-tool/google-sheets-write-mcp-server'

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