Skip to main content
Glama

Import to Google Doc

import_to_google_doc

Imports Markdown, DOCX, TXT, HTML, RTF, or ODT files into Google Docs with automatic conversion. Supports upload from local file path, URL, or text content.

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. 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
user_google_emailYesThe user's Google email address. Required.
file_nameYesThe name for the new Google Doc (extension will be ignored).
contentNoText content for text-based formats. Use only for short snippets or content already in memory.
file_pathNoLocal 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.
file_urlNoRemote URL to fetch the file from (http/https).
source_formatNoSource format hint ('md', 'markdown', 'docx', 'txt', 'html', 'rtf', 'odt'). Auto-detected from file_name extension if not provided.
folder_idNoThe ID of the parent folder. Defaults to 'root'.root

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description reveals conversion quality (preserves formatting), memory/performance caveats for file_path (non-streaming, risk of memory overload), and auto-detection of source format. Discloses side effects (file creation in Google Drive) consistent with openWorldHint.

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?

Three sentences: first defines purpose, second adds conversion detail, third provides usage guidance. No filler, front-loaded with essential information. Each sentence earns its place.

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?

Given the tool's complexity (7 params, output schema exists), the description covers core purpose, supported formats, conversion behavior, and parameter selection strategy. It does not need to mention authentication or return values (output schema covers returns). Sibling differentiation is implicit. Complete for a user to understand when and how to invoke this tool.

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 baseline is 3. The description adds value by explaining when to use each file source parameter (content vs file_path vs file_url) and warns about file_path limitations, beyond what the schema describes. Does not repeat but enhances parameter understanding.

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 clearly states the tool imports files in multiple formats (Markdown, DOCX, etc.) into Google Docs format, specifies automatic conversion, and implicitly distinguishes from sibling tools like import_to_google_sheets by targeting Google Docs.

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?

Provides specific guidance: for batch operations, prefer file_path to avoid loading content into context; describes when to use content (short snippets) vs file_path (larger files with memory warnings) vs file_url. Lacks explicit alternatives to this tool among siblings, but the given guidance is clear and actionable.

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/chadvdwww-hash/worksuite-mcp'

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