google-workspace-mcp

docs_create

Create a new Google Doc with a specified title and optional initial body text. Populate the document content right away by passing text.

Instructions

Create a new Google Doc with optional initial text content.

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"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`body_text`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It mentions core behavior (creates a doc, optional initial text) but does not disclose side effects like Drive storage, authentication needs, or that it returns a document ID. For a simple create operation, this is borderline adequate but not rich.

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 a single, concise sentence that is immediately front-loaded with the key verb and resource. Every word adds value, with no unnecessary filler or redundant detail.

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?

For a simple 2-parameter creation tool with an output schema, the description covers the essential action and optional parameter. It does not mention that the doc is created in Drive or any prerequisites, but given the tool's simplicity, this is reasonably 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 0%, so the description must compensate. It clarifies that body_text is optional and serves as initial content, but it does not explicitly explain the title parameter (though that is self-evident from the schema property name). It adds some value but not comprehensive parameter documentation.

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 ('Create'), the resource ('a new Google Doc'), and an optional scope ('with optional initial text content'). This distinguishes it from siblings like docs_append_text or drive_create_file, which modify or create other file types.

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 implies usage for creating a new Google Doc, but provides no explicit guidance on when to prefer this over related tools, no exclusions, and no alternative tool mentions. The context from sibling names helps, but the description itself lacks direct usage clarity.

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

Deploy Server