google-workspace-mcp-server

Create Google Document

docs_create_document

Create a new Google Doc with a specified title and optional initial text content. Instantly generate a document to start working.

Instructions

Create a new Google Doc with an optional initial body.

Args:

title (string): The title for the new document
body_content (string, optional): Initial text content for the document body

Returns: { "documentId": string, "title": string, "revisionId": string }

Examples:

Create empty doc: title="Meeting Notes"
Create with content: title="Draft", body_content="Hello World"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "docs_create_document"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	The title for the new document
`body_content`	No	Optional initial text content for the document body

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.3May 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already indicate this is a non-read-only, non-idempotent, non-destructive operation. The description adds useful behavioral context by specifying the return structure (documentId, title, revisionId) and providing examples of creating empty versus content-bearing documents. It does not contradict 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?

The description is well-structured and concise: a one-sentence summary, a clear argument list, a return type, and practical examples. Every section contributes directly to understanding how to use the tool, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity and the rich schema coverage, the description is nearly complete for an agent to invoke it correctly. It includes parameter details and return format. However, it omits any mention of when to use this tool versus alternatives (like docs_batch_update) or any side effects (e.g., the document appears in Drive), which would make it fully complete.

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?

Schema description coverage is 100%, and the description lists both parameters with explanations that mirror the schema nearly verbatim. It adds some value through usage examples, but the parameter semantics are already fully captured by the schema, so the description provides no significant new meaning beyond what the schema offers.

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: 'Create a new Google Doc with an optional initial body.' This uses a specific verb ('Create') and resource ('Google Doc'), and it distinguishes from siblings like docs_get_document (read) and docs_batch_update (modify), as well as sheets_create_spreadsheet (different resource type).

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?

The description provides clear context for when to use the tool (creating a new document, with or without content) through the summary and examples. However, it does not explicitly mention alternatives or when not to use this tool versus other sibling tools, so it lacks explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.