Skip to main content
Glama
YatharthLakhera

Custom Google Drive MCP

Import to Google Doc

import_to_google_doc

Import files from Markdown, DOCX, TXT, HTML, RTF, or ODT into Google Docs format. Convert via content, file path, or URL with 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. 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_emailNoThe user's Google email address. Required.user@gmail.com
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
Behavior4/5

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

The description discloses automatic conversion and formatting preservation. It warns about file_path loading into memory and advises against very large files. Annotations (readOnlyHint=false, destructiveHint=false) are consistent, and the description adds memory and size considerations beyond annotations.

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, each serving a purpose: main action, conversion behavior, and usage advice. No wasted words, well-structured with key information upfront.

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 a single-purpose import tool with an output schema (presumably documenting return values), the description covers input sources, formats, conversion behavior, and practical constraints. It is complete for an AI agent to invoke correctly.

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%, but the description adds meaningful advice: prefer file_path for batch operations, use content only for short snippets, and avoid huge files. This enhances understanding beyond the schema's basic 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 clearly states the verb 'imports' and the resource 'file into Google Docs format' with automatic conversion. It lists supported formats, making the purpose unambiguous. The tool is distinct from siblings like create_file or update_drive_file, which do not involve conversion to 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides guidance on parameter selection (prefer file_path for batch operations, content for short snippets) but does not explicitly compare to sibling tools. It lacks when-to-use versus alternatives like create_file or update_drive_file, so usage context is partial.

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/YatharthLakhera/claude-gdrive-mcp'

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