grr

Overview Schema Source Related Servers Discussions Admin

sheets.spreadsheets.sheets.copyTo

Copies a single sheet from one spreadsheet into another and returns the new sheet's properties. Use it to duplicate tabs across files by providing the source spreadsheet, sheet ID, and destination ID.

Instructions

Copies a single sheet from a spreadsheet to another spreadsheet. Returns the properties of the newly created sheet [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON CopySheetToAnotherSpreadsheetRequest object accepting destinationSpreadsheetId; pass it via params or whole via body_file

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`sheetId`	Yes	[URL path segment] The ID of the sheet to copy.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON CopySheetToAnotherSpreadsheetRequest object.
`request_body`	No	Request body of type CopySheetToAnotherSpreadsheetRequest: pass it via `params` (merged into the built body) or whole via `body_file`.
`spreadsheetId`	Yes	[URL path segment] The ID of the spreadsheet containing the sheet to copy.

Output Schema

Name	Required	Description	Default
`index`	No
`title`	No
`hidden`	No
`sheetId`	No
`tabColor`	No
`sheetType`	No
`rightToLeft`	No
`tabColorStyle`	No
`gridProperties`	No
`dataSourceSheetProperties`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON CopySheetToAnotherSpreadsheetRequest object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type CopySheetToAnotherSpreadsheetRequest: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "destinationSpreadsheetId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / sheetId / description

Previous value: -"The ID of the sheet to copy."New value: +"[URL path segment] The ID of the sheet to copy."

addedInput schema / properties / sheetId / format
```
Added value: +"int32"
```

changedInput schema / properties / spreadsheetId / description

Previous value: -"The ID of the spreadsheet containing the sheet to copy."New value: +"[URL path segment] The ID of the spreadsheet containing the sheet to copy."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "dataSourceSheetProperties": {
+      "properties": {
+        "columns": {
+          "items": {
+            "properties": {
+              "formula": {
+                "type": "string"
+              },
+              "reference": {
+                "properties": {
+                  "name": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "dataExecutionStatus": {
+          "properties": {
+            "errorCode": {
+              "enum": [
+                "DATA_EXECUTION_ERROR_CODE_UNSPECIFIED",
+                "TIMED_OUT",
+                "TOO_MANY_ROWS",
+                "TOO_MANY_COLUMNS",
+                "TOO_MANY_CELLS",
+                "ENGINE",
+                "PARAMETER_INVALID",
+                "UNSUPPORTED_DATA_TYPE",
+                "DUPLICATE_COLUMN_NAMES",
+                "INTERRUPTED",
+                "CONCURRENT_QUERY",
+                "OTHER",
+                "TOO_MANY_CHARS_PER_CELL",
+                "DATA_NOT_FOUND",
+                "PERMISSION_DENIED",
+                "MISSING_COLUMN_ALIAS",
+                "OBJECT_NOT_FOUND",
+                "OBJECT_IN_ERROR_STATE",
+                "OBJECT_SPEC_INVALID",
+                "DATA_EXECUTION_CANCELLED"
+              ],
+              "type": "string"
+            },
+            "errorMessage": {
+              "type": "string"
+            },
+            "lastRefreshTime": {
+              "type": "string"
+            },
+            "state": {
+              "enum": [
+                "DATA_EXECUTION_STATE_UNSPECIFIED",
+                "NOT_STARTED",
+                "RUNNING",
+                "CANCELLING",
+                "SUCCEEDED",
+                "FAILED"
+              ],
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "dataSourceId": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "gridProperties": {
+      "properties": {
+        "columnCount": {
+          "type": "integer"
+        },
+        "columnGroupControlAfter": {
+          "type": "boolean"
+        },
+        "frozenColumnCount": {
+          "type": "integer"
+        },
+        "frozenRowCount": {
+          "type": "integer"
+        },
+        "hideGridlines": {
+          "type": "boolean"
+        },
+        "rowCount": {
+          "type": "integer"
+        },
+        "rowGroupControlAfter": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "hidden": {
+      "type": "boolean"
+    },
+    "index": {
+      "type": "integer"
+    },
+    "rightToLeft": {
+      "type": "boolean"
+    },
+    "sheetId": {
+      "type": "integer"
+    },
+    "sheetType": {
+      "enum": [
+        "SHEET_TYPE_UNSPECIFIED",
+        "GRID",
+        "OBJECT",
+        "DATA_SOURCE"
+      ],
+      "type": "string"
+    },
+    "tabColor": {
+      "properties": {
+        "alpha": {
+          "type": "number"
+        },
+        "blue": {
+          "type": "number"
+        },
+        "green": {
+          "type": "number"
+        },
+        "red": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "tabColorStyle": {
+      "properties": {
+        "rgbColor": {
+          "properties": {
+            "alpha": {
+              "type": "number"
+            },
+            "blue": {
+              "type": "number"
+            },
+            "green": {
+              "type": "number"
+            },
+            "red": {
+              "type": "number"
+            }
+          },
+          "type": "object"
+        },
+        "themeColor": {
+          "enum": [
+            "THEME_COLOR_TYPE_UNSPECIFIED",
+            "TEXT",
+            "BACKGROUND",
+            "ACCENT1",
+            "ACCENT2",
+            "ACCENT3",
+            "ACCENT4",
+            "ACCENT5",
+            "ACCENT6",
+            "LINK"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses HTTP POST, that it creates/triggers a change, and that it is refused under --readonly safety profiles, plus the request body type. It stops short of auth/permission requirements, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and clear, but the return value is explained twice ('returns the properties of the newly created sheet' and 'Returns the API's response resource as JSON') even though an output schema exists, which is wasted phrasing.

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?

Covers behavior, safety profile, and request body plumbing; the output schema handles returns, so the description is essentially complete. Only auth/prerequisite detail is missing.

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?

Schema coverage is 100% and every parameter is already documented, so the baseline is 3. The description's mention of destinationSpreadsheetId and the params/body_file plumbing largely restates what the schema already says, adding little beyond it.

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?

States a specific verb (Copies) applied to a single resource (one sheet) with explicit scope (from a spreadsheet to another spreadsheet). This clearly distinguishes it from siblings like drive.files.copy or sheet value operations.

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?

It implies when it applies (a sheet-level copy across spreadsheets) and notes it is refused under --readonly, but never names an alternative or states exclusions versus other copy paths (e.g., sheets.spreadsheets.batchUpdate CopySheetToAnotherSpreadsheet). Usage is inferable but not guided.

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

Deploy Server