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

Import to Google Doc

import_to_google_doc

Convert Markdown, DOCX, TXT, HTML, RTF, or ODT files into editable Google Docs documents with automatic formatting preservation.

Instructions

Imports a file (Markdown, DOCX, TXT, HTML, RTF, ODT) into Google Docs format with automatic conversion.

Google Drive automatically converts the source file to native Google Docs format, preserving formatting like headings, lists, bold, italic, etc. 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

Name	Required	Description	Default
`content`	No	Text content for text-based formats. Use only for short snippets or content already in memory.
`file_url`	No	Remote URL to fetch the file from (http/https).
`file_name`	Yes	The name for the new Google Doc (extension will be ignored).
`file_path`	No	Local file path or file:// URL for any supported format (MD, TXT, HTML, DOCX, ODT, RTF). 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 ('md', 'markdown', 'docx', 'txt', 'html', 'rtf', 'odt'). Auto-detected from file_name extension if not provided.
`base64_content`	No	Standard base64-encoded bytes for a binary source such as DOCX or ODT.
`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.

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 binary source such as DOCX or ODT."
+}

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.5/5.0

Behavior4/5

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

The description adds behavioral context beyond annotations by explaining that Google Drive automatically converts the file, preserves formatting, and that binary sources can be passed as base64_content. It also discloses that file_path can still load files into memory, which is useful performance-related behavior.

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, front-loaded with the core action, and every sentence serves a purpose. It avoids restating the parameter schema and keeps additional guidance brief.

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?

The description, combined with 100% schema description coverage and an output schema, provides enough information to select and invoke the tool correctly. It covers supported formats, conversion behavior, input modes, and practical guidance for larger files.

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 value by advising when to prefer file_path for batch operations and by clarifying that binary sources may use base64_content, going beyond what the schema fields already state.

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 ('Imports'), a clear target resource ('Google Docs format'), and enumerates the supported source formats. It differentiates from sibling import tools (import_to_google_slides, import_to_google_sheets) by making the destination format explicit.

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 clear context on when to use file_path versus content/base64_content, especially for batch operations, telling callers to avoid loading full file contents into context. It does not explicitly contrast against sibling tools, but the intended use case is clear.

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

Deploy Server