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

Import to Google Sheets

import_to_google_sheets

Convert XLSX, XLS, ODS, CSV, or TSV files into Google Sheets format, preserving rows, columns, and values, and save them to Google Drive.

Instructions

Imports a spreadsheet (XLSX, XLS, ODS, CSV, TSV) into Google Sheets format with automatic conversion.

Google Drive automatically converts the source spreadsheet to native Google Sheets format, preserving rows, columns, sheets, and values. Binary sources may be passed directly as base64_content. On a local server a file on disk can also be passed by path (preferred for batch operations, so callers do not need to load full file contents into their context).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`content`	No	Text content for text-based formats (CSV, TSV). Use only for short snippets or content already in memory.
`file_url`	No	Remote URL to fetch the spreadsheet from (http/https).
`file_name`	Yes	The name for the new Google Sheets spreadsheet (extension will be ignored).
`file_path`	No	Local file path or file:// URL for any supported format (XLSX, XLS, ODS, CSV, TSV). Appropriate for larger files than content, but file_path may still load the file into memory or perform non-streaming reads. Avoid very large files that could exceed memory or time limits; use streaming/chunked uploads or an alternative API for huge files.
`folder_id`	No	The ID of the parent folder. Defaults to 'root'.	root
`base64_sha256`	No	Expected SHA-256 of decoded base64_content. Recommended for binary payload integrity checks.
`source_format`	No	Source format hint ('xlsx', 'xls', 'ods', 'csv', 'tsv'). Auto-detected from file_name extension if not provided.
`base64_content`	No	Standard base64-encoded bytes for an XLSX, XLS, or ODS source.
`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.

Changed12 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / base64_content / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / base64_content / type
```
Added value: +"string"
```
- removedInput schema / properties / base64_sha256 / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / base64_sha256 / type
```
Added value: +"string"
```
- removedInput schema / properties / content / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / content / type
```
Added value: +"string"
```
- removedInput schema / properties / file_path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / file_path / type
```
Added value: +"string"
```
- removedInput schema / properties / file_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / file_url / type
```
Added value: +"string"
```
- removedInput schema / properties / source_format / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / source_format / type
```
Added value: +"string"
```

Changed2 schema fields changedv1.25.2Aug 30, 2026

addedInput schema / properties / base64_content

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Standard base64-encoded bytes for an XLSX, XLS, or ODS source."
+}

addedInput schema / properties / base64_sha256

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Expected SHA-256 of decoded base64_content. Recommended for binary payload integrity checks."
+}

Addedv1.0.1Jul 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses meaningful behavioral detail beyond annotations: Google Drive automatically converts the source, preserving rows, columns, sheets, and values. Annotations already signal that this is a non-read-only, non-idempotent operation, and the description adds context about the conversion behavior without contradicting them.

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 compact and front-loaded: the first sentence states the core purpose, and the second paragraph adds only behavioral and usage context that the schema does not fully carry. Every sentence earns its place with no redundant filler.

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's 9 parameters and multiple input pathways, the description covers the essential behavior, source-format options, and batch-operation guidance. It could more explicitly state that exactly one input source (content, file_url, file_path, or base64_content) should be provided, but the schema already documents each option and the output schema covers return expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds extra selection guidance beyond the schema by explaining that binary sources may be passed directly as base64_content and that file_path is preferred for batch operations to save caller context. This helps the agent choose between the multiple mutually-exclusive input methods.

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 ('Imports') and resource ('a spreadsheet... into Google Sheets format'), and enumerates the supported source formats (XLSX, XLS, ODS, CSV, TSV). This clearly distinguishes it from sibling import tools like import_to_google_doc and import_to_google_slides by naming the target format.

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 gives actionable guidance on how to supply content: base64_content for binary sources, file path preferred for batch operations to avoid loading full file contents. It does not explicitly say when to choose this tool over sibling import tools, but the target format is self-evident and the tool name makes the use case clear.

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

Deploy Server