Google Sheets and Drive MCP

by Runemal

Overview Schema Source Related Servers Discussions Admin

Python

Remote

copy_sheet

Duplicate a sheet within a Google Sheets spreadsheet by specifying the source sheet name and a new sheet name.

Instructions

Duplicate one complete sheet within the same 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>",
      "source_sheet_name": "<source_sheet_name>",
      "new_sheet_name": "<new_sheet_name>"
    },
    "name": "copy_sheet"
  }
}

Input Schema

Name	Required	Description	Default
`new_sheet_name`	Yes
`spreadsheet_id`	Yes
`source_sheet_name`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the basic action without disclosing details like whether formatting, formulas, or data validation are copied, or if the source sheet remains unchanged. The minimal description lacks behavioral context.

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?

The description is a single, efficient sentence that captures the core functionality. It is front-loaded and to the point. However, it could include a bit more context without becoming verbose.

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?

Given the existence of an output schema, the description could be slightly lighter on return details, but it fails to mention important context such as that the source sheet is preserved, cannot copy to another spreadsheet, or any constraints on sheet names. The description is inadequate for a complete understanding.

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 coverage is 0% and the description does not explain any of the three parameters beyond their names. It adds no semantic value, e.g., it does not specify that 'source_sheet_name' must match an existing sheet name exactly or that 'new_sheet_name' must be unique.

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 'duplicate' and explicitly names the resource 'sheet' and context 'within the same spreadsheet'. It clearly distinguishes from sibling tools like 'copy_range' (copies a range, not entire sheet) and 'create_sheet' (creates new blank sheet).

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?

No guidance provided on when to use this tool versus alternatives. For instance, it doesn't state that the copy must be within the same spreadsheet or mention when to use 'copy_range' instead. Users must infer usage from the description alone.

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