Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Create Sheet

create_sheet

Create a new sheet in a Google Spreadsheet or duplicate an existing sheet by providing the spreadsheet ID and user email.

Instructions

Creates a new sheet or duplicates an existing sheet (user_google_email: str, spreadsheet_id: str, sheet_name: Optional[str] = None, source_sheet_name: Optional[str] = None, insert_sheet_index: Optional[int] = None).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sheet_name`	No
`spreadsheet_id`	Yes
`source_sheet_name`	No
`user_google_email`	Yes
`insert_sheet_index`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / insert_sheet_index / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / insert_sheet_index / type
```
Added value: +"integer"
```
- removedInput schema / properties / sheet_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / sheet_name / type
```
Added value: +"string"
```
- removedInput schema / properties / source_sheet_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / source_sheet_name / type
```
Added value: +"string"
```

Changed13 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / insert_sheet_index

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedInput schema / properties / service

Removed value: -{
-  "title": "service",
-  "type": "string"
-}

addedInput schema / properties / sheet_name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / sheet_name / default
```
Added value: +null
```
removedInput schema / properties / sheet_name / title
```
Removed value: -"Sheet Name"
```
removedInput schema / properties / sheet_name / type
```
Removed value: -"string"
```

addedInput schema / properties / source_sheet_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

removedInput schema / properties / spreadsheet_id / title
```
Removed value: -"Spreadsheet Id"
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

changedInput schema / required

Previous value: -[
-  "service",
-  "user_google_email",
-  "spreadsheet_id",
-  "sheet_name"
-]New value: +[
+  "user_google_email",
+  "spreadsheet_id"
+]

removedInput schema / title
```
Removed value: -"create_sheetArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.0Jun 10, 2025

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already signal that this is a mutating, non-destructive, non-idempotent operation. The description adds the dual create-vs-duplicate behavior, but it does not disclose what happens on duplicate, name conflicts, copying scope, or required authorization context.

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?

The opening clause is short and front-loaded, but the inline signature is redundant with the input schema and adds clutter. The description is not overly long, yet not every part earns its place.

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?

With five parameters and zero parameter descriptions in the schema, a single functional line is insufficient. The mode-selection logic between sheet_name and source_sheet_name is absent, so an agent could invoke the tool with conflicting or misunderstood options.

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 description coverage is 0%, so the description needed to explain the parameters. It only restates the Python-style signature, which largely duplicates the input schema's types and defaults, and gives no actual meaning for fields like source_sheet_name or insert_sheet_index.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action ('Creates a new sheet or duplicates an existing sheet') and the resource, so an agent can tell what the tool does. However, it does not differentiate from close siblings such as manage_sheet_tab or create_spreadsheet, so it stops short of a 5.

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?

The description offers no guidance about when to use this tool versus related tools like manage_sheet_tab, create_spreadsheet, or copy_drive_file. It states what the tool does but not the conditions that should lead an agent to select it.

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

Deploy Server