Skip to main content
Glama

create_doc

Create a new Google Doc with optional initial content. Insert plain text or markdown to format headings, lists, and text styling.

Instructions

Creates a new Google Doc and optionally inserts initial content.

After creation, the document body starts at index 1. A new empty doc has total length 2 (one section break at index 0, one newline at index 1).

To build a rich document after creation, use batch_update_doc with insert_text operations using end_of_segment=true to append content sequentially without calculating indices. Then call inspect_doc_structure to get exact positions before applying formatting in a separate batch call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesUser's Google email address
titleYesTitle of the new document
contentNoOptional initial content to insert.
format_as_markdownNoIf True, parses `content` as markdown and inserts it with native Docs formatting (headings, bold, italic, bullet/numbered/ checkbox lists). Supports `# H1`-`### H3`, `**bold**`, `*italic*`, `- bullets`, `1. numbered`, and `- [ ] checkbox` (also `- [x]`). Default False (insert as plain text).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Details document body indexing (starts at 1, empty doc length 2), markdown parsing behavior, and sequential workflow. With no annotations, description effectively discloses structural and behavioral traits.

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?

Three paragraphs with no wasted sentences. Front-loaded with main purpose, then structural details, then workflow. Efficiently organized.

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 output schema exists, description need not explain return values. Covers creation, structure, and complete workflow guidance with sibling tool references. Sufficient for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage, so baseline 3. Description adds marginal context about document indexing but largely restates schema info. No significant additional parameter detail.

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?

Clearly states it creates a new Google Doc with optional initial content. Specifically names the resource and action, distinguishing it from siblings like batch_update_doc and insert_doc_markdown.

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 explicit after-creation workflow: use batch_update_doc for rich content and inspect_doc_structure before formatting. Implicitly differentiates when to use this vs other tools, though no direct 'when not to use' statement.

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/HuntsDesk/ve-gws'

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