Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Import to Google Slides

import_to_google_slides

Import PPTX, PPT, or ODP presentations into Google Slides with automatic conversion, preserving slides, layouts, text, and images.

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. For batch operations, prefer file_path for files on disk so callers do not need to load full file contents into their context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_urlNoRemote URL to fetch the presentation from (http/https).
file_nameYesThe name for the new Google Slides presentation (extension will be ignored).
file_pathNoLocal 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_idNoThe ID of the parent folder. Defaults to 'root'.root
base64_sha256NoExpected SHA-256 of decoded base64_content. Recommended for binary payload integrity checks.
source_formatNoSource format hint ('pptx', 'ppt', 'odp'). Auto-detected from file_name extension if not provided.
base64_contentNoStandard base64-encoded bytes for a PPTX or ODP source.
user_google_emailYesThe user's Google email address. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.25.2
    • 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."
+}
  2. Addedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

It discloses automatic Google Drive conversion, preservation of slides/layouts/text/images, and the important caveat that file_path may still load the file into memory or perform non-streaming reads, with advice to avoid very large files. This adds substantial behavioral context beyond the sparse annotations and contains no contradiction.

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 three focused sentences: purpose first, then conversion behavior, then input-method guidance. Every sentence earns its place, and there is no redundant or vague wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter import tool, the description plus schema and output schema cover supported formats, conversion behavior, input methods, destination folder default, and performance/memory caveats. The description does not need to enumerate every parameter because the schema already does so comprehensively.

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, but the description adds useful semantics for choosing between base64_content and file_path, especially for batch operations and avoiding context bloat. It does not need to repeat the schema's detailed parameter descriptions.

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: 'Imports a presentation (PPTX, PPT, ODP) into Google Slides format with automatic conversion.' It names supported source formats and the destination format, which clearly distinguishes it from siblings 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 practical guidance: binary sources may use base64_content, and batch operations should prefer file_path to avoid loading full contents into context. However, it does not explicitly compare this tool to alternatives such as create_presentation or other import tools, so when-not-to-use guidance is only implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorwilsdon/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server