Skip to main content
Glama

create_doc

Create Google Docs with optional initial content and markdown formatting. Specify user email and title to generate documents programmatically.

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the document structure after creation (body starts at index 1, total length 2), the workflow for subsequent operations, and the optional markdown parsing capability. However, it doesn't mention permissions, rate limits, or error conditions, which would be helpful for a mutation tool.

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 well-structured and front-loaded, with the core purpose in the first sentence. Every subsequent sentence adds valuable context about document structure, workflow, and alternatives without redundancy. It's appropriately sized for the tool's complexity.

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 (mutation with 4 parameters), 100% schema coverage, and presence of an output schema, the description is complete enough. It covers purpose, usage guidelines, behavioral context, and workflow integration without needing to repeat schema details or explain return values.

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?

The schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description doesn't add significant meaning beyond what's in the schema, though it implies the 'content' parameter's role in initial insertion. Baseline 3 is appropriate when the schema does the heavy lifting.

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's purpose with specific verbs ('Creates a new Google Doc') and resources ('Google Doc'), distinguishing it from siblings like 'create_spreadsheet' or 'create_presentation'. It also specifies optional functionality ('optionally inserts initial content'), making the purpose explicit and distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives, naming specific sibling tools ('batch_update_doc', 'inspect_doc_structure') for post-creation operations. It explains the workflow for building rich documents after creation, offering clear alternatives and sequencing advice.

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