Skip to main content
Glama
Sign In
google-docs-mcp

google-docs-mcp

by dbuxton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

docs_create

Create a new Google Doc with an optional opening paragraph, providing a clean starting point for document generation while preserving version history.

Instructions

Create a new Google Doc with an optional initial paragraph of text.

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

NameRequiredDescriptionDefault
titleYesDocument title
initial_textNoOptional first paragraph content

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It states the core action (creates a new Google Doc) and the optional initial paragraph, but does not mention side effects such as where the doc is stored, whether creation can be repeated, or any permission requirements. This is adequate but leaves some behavior implicit.

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, tightly worded sentence that conveys the purpose and the optional parameter without any redundancy. Every word adds value, and the most important information is front-loaded.

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 only two simple parameters and an existing output schema, the description is sufficient for an agent to understand the tool's core function and call it correctly. It does not specify permissions or location of the created doc, but these are not essential for a basic create operation with structured schema support.

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 input schema already fully describes both parameters (title and initial_text) with 100% coverage. The description adds minimal extra meaning beyond restating that initial_text is optional and used as the first paragraph, so it does not meaningfully elevate the semantic value.

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 states a specific verb and resource: 'Create a new Google Doc'. The word 'new' and the optional initial paragraph distinguish it clearly from sibling tools like docs_insert_after, docs_append, and docs_get, which all operate on existing documents.

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 clearly implies this tool is for creating new documents, which sets apart from siblings that edit or read existing docs. However, it does not explicitly list alternatives or state when not to use the tool, so it stops short of a full exclusionary guideline.

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

Deploy Server

Other Tools