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

Import to Google Slides

import_to_google_slides

Imports PowerPoint or OpenDocument presentations into Google Slides format, automatically converting slides, layouts, text, and images into a native editable deck.

Instructions

Imports a presentation (PPTX, PPT, ODP) into Google Slides format with automatic conversion.

Google Drive automatically converts the source presentation to native Google Slides format, preserving slides, layouts, text, and images. 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

Name	Required	Description	Default
`file_url`	No	Remote URL to fetch the presentation from (http/https).
`file_name`	Yes	The name for the new Google Slides presentation; the extension is dropped from the title. Without 'source_format', its extension also sets the format of 'base64_content' (e.g. 'Deck.pptx').
`file_path`	No	Local file path or file:// URL for any supported format (PPTX, PPT, ODP). 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 ('pptx', 'ppt', 'odp'). Auto-detected from file_name extension if not provided.
`base64_content`	No	Standard base64-encoded bytes for a PPTX or ODP source.
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.0Oct 24, 2026

changedInput schema / properties / file_name / description

Previous value: -"The name for the new Google Slides presentation (extension will be ignored)."New value: +"The name for the new Google Slides presentation; the extension is dropped from the title. Without 'source_format', its extension also sets the format of 'base64_content' (e.g. 'Deck.pptx')."

Changed10 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 / 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 a PPTX or ODP 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

A3.9/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that Drive performs automatic conversion preserving slides, layouts, text, and images. It also notes that local file paths are preferred for batch operations to avoid loading full contents into caller context. It does not explicitly discuss duplicate behavior or non-idempotency, but the annotations already mark the tool as non-idempotent and non-destructive.

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 front-loaded and reasonably concise, first stating the import behavior and then adding source-method guidance. There is minor redundancy between 'with automatic conversion' and 'automatically converts', but no significant wasted text.

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?

With an output schema, complete parameter descriptions, and annotations covering mutation and openness, the description gives enough context to invoke the tool correctly. It is slightly incomplete only in not routing the agent among similar import/create siblings.

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 description coverage is 100%, so the schema already documents all parameters in detail. The description adds useful high-level context about base64_content and file_path usage, but it does not add meaning beyond the schema for the remaining parameters such as file_url, folder_id, or base64_sha256.

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 states a specific verb and resource: importing PPTX, PPT, or ODP presentations into native Google Slides format with automatic conversion. This clearly distinguishes it from creation and spreadsheet/doc import siblings.

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 explains source input methods such as base64_content and local file_path, with file_path preferred for batch operations. However, it does not explicitly say when to use this tool versus siblings like create_presentation or import_to_google_doc, nor when not to use it.

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

Deploy Server