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

Create Spreadsheet

create_spreadsheet

Create a new Google Spreadsheet with custom sheet names and a chosen folder. Specify the user's email address and title to generate the file.

Instructions

Creates a new Google Spreadsheet.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	Yes	The title of the new spreadsheet. Required.
`folder_id`	No	The ID of the parent folder. Defaults to 'root'. For shared drives, this must be a folder ID within the shared drive.	root
`sheet_names`	No	List of sheet names to create. If not provided, creates one sheet with default name.
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.28.0Sep 24, 2026

addedInput schema / properties / folder_id

Added value: +{
+  "default": "root",
+  "description": "The ID of the parent folder. Defaults to 'root'. For shared\ndrives, this must be a folder ID within the shared drive.",
+  "type": "string"
+}

removedInput schema / properties / sheet_names / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / sheet_names / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / sheet_names / type
```
Added value: +"array"
```

Changed11 schema fields changedv1.0.1Jul 31, 2026

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

removedInput schema / properties / service

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

addedInput schema / properties / sheet_names / description

Added value: +"List of sheet names to create. If not provided, creates one sheet with default name."

removedInput schema / properties / sheet_names / title
```
Removed value: -"Sheet Names"
```

addedInput schema / properties / title / description

Added value: +"The title of the new spreadsheet. Required."

removedInput schema / properties / title / title
```
Removed value: -"Title"
```
addedInput schema / properties / user_google_email / description
```
Added value: +"The user's Google email address. Required."
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

changedInput schema / required

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

removedInput schema / title

Removed value: -"create_spreadsheetArguments"

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

Behavior2/5

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

The description only restates the creation action and adds no behavioral context beyond the annotations. It does not disclose where the spreadsheet is created by default, authentication or permission requirements, or resulting runtime behavior. This is not a contradiction, but it adds no value beyond the structured signals.

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 description is a single, short sentence with no redundancy. However, it is under-specified: it essentially repeats the tool name and does not structure any key decision-relevant facts such as defaults or related tool choices.

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 four parameters, two required fields, an output schema, and a large sibling tool set, a one-sentence description is insufficient. It lacks usage boundaries against create_sheet/import_to_google_sheets and does not explain behavior beyond 'create', leaving the agent under-informed for correct selection and invocation.

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 schema already provides 100% parameter coverage with descriptions, including required user_google_email and title, the default for folder_id, and the behavior of sheet_names. The description itself adds no parameter information, but the high schema coverage justifies a baseline score of 3.

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 states the action and resource: 'Creates a new Google Spreadsheet.' This is not a tautology and conveys the core operation accurately. However, it does not explicitly differentiate from sibling tools like create_sheet or import_to_google_sheets, so it lacks sibling distinction.

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 provides no guidance on when to use this tool versus alternatives such as create_sheet, import_to_google_sheets, or create_drive_file. An agent must infer the right choice from the tool name rather than from explicit usage guidance.

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

Deploy Server