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

Import to Google Slides

import_to_google_slides

Convert PPTX, PPT, or ODP files into editable Google Slides presentations. Provide a file path, URL, or base64 content to import and auto-convert with layout and image preservation.

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

TableJSON 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 (extension will be ignored).
`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

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.3/5.0

Behavior4/5

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

The description discloses that Google Drive automatically converts and preserves slides, layouts, text, and images, adding behavioral context beyond the annotations. The practical note about batch operations and avoiding full-content loads also helps set expectations. No contradiction with the annotations.

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 compact and front-loaded with the core purpose, followed by one practical paragraph on input modes. Every sentence earns its place, and the length is appropriate for a tool with 8 parameters.

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 output schema and full schema coverage, the description appropriately focuses on conversion behavior and input routing. It does not explain every parameter, but it contextualizes the most ambiguous optional inputs and leaves routine details to the schema.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the tradeoff between base64_content and file_path and why file_path is preferred for batch operations, which helps select among the optional input parameters.

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 opening sentence names the concrete action (imports), the resource type (presentation), the supported source formats (PPTX, PPT, ODP), and the destination format (Google Slides). This clearly distinguishes it from sibling import tools like import_to_google_doc and import_to_google_sheets.

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 concrete input-mode guidance by recommending file_path for batch operations and contrasting it with base64_content, so callers can choose the right parameter. It does not explicitly name sibling tools or exclusions, but the target format 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