Skip to main content
Glama
Skeptomenos

google-workspace-mcp-advanced

by Skeptomenos

create_doc

Create a new Google Doc and insert content, with automatic Markdown-to-formatting conversion or plain text insertion.

Instructions

Creates a new Google Doc and optionally inserts initial content.

When parse_markdown=True (default), the content is parsed as Markdown and converted to native Google Docs formatting (headings, bold, italic, lists, links, code blocks, blockquotes). Set parse_markdown=False to insert content as plain text without any formatting.

Args: user_google_email: User's Google email address. title: The title of the new document. content: Optional initial content. Interpreted as Markdown by default. parse_markdown: If True (default), parse content as Markdown and apply formatting. If False, insert content as plain text. checklist_mode: Checklist rendering mode for markdown task lists: unicode (default) or native. mention_mode: Mention rendering mode for markdown mentions: text (default) or person_chip. dry_run: When True (default), preview create/update actions without executing them.

Returns: str: Confirmation message with document ID and link.

Examples: # Create doc with Markdown content (default behavior) create_doc(title="My Doc", content="# Heading\n\nBold text")

# Create doc with native checklist bullets
create_doc(title="Checklist Doc", content="- [ ] One\n- [x] Two", checklist_mode="native")

# Create doc with plain text (no Markdown parsing)
create_doc(title="Plain Doc", content="# This is literal text", parse_markdown=False)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
titleYes
contentNo
parse_markdownNo
checklist_modeNounicode
mention_modeNotext
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It thoroughly describes behavior for parse_markdown, checklist_mode, mention_mode, and dry_run, and includes examples. However, it omits information about required permissions, rate limits, or edge cases like duplicate titles.

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 with Args, Returns, and Examples sections, front-loading the purpose. Every sentence adds value, neither verbose nor terse, making it easy to parse for an AI agent.

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 parameters, 2 required, output schema exists without return value details), the description is complete. It covers all parameters, return format, and provides practical examples, ensuring the agent can use the tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, meaning no parameter descriptions in the schema. The description compensates fully by explaining each of the 7 parameters, including defaults, accepted values (e.g., checklist_mode options), and effects with examples. This adds essential meaning beyond the bare schema.

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 action ('creates a new Google Doc') and the resource ('Google Doc'), with specific detail about optional initial content. It distinguishes from siblings by focusing on Google Docs creation with markdown parsing, though not explicit about alternatives.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like create_drive_file or update_google_doc. The description explains parameters and behavior but does not provide selection criteria or exclusion cases.

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/Skeptomenos/google-workspace-mcp-advanced'

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