Skip to main content
Glama
ammarqaisar11a55

Google Docs MCP

by ammarqaisar11a55
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Google Doc

create_document

Creates a new Google Docs document in Google Drive with a title and optional plain-text content, returning the document ID, title, and URL for further editing.

Instructions

Create a new Google Docs document with the given title in the user’s Google Drive, optionally filled with initial plain text. Returns the new documentId, title and URL. Headings, bold text and lists are not created from the text: apply them afterwards with set_paragraph_style, format_text or create_bulleted_list (use find_text or get_document for the indexes). To add more content later use append_text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the new document, e.g. "FYP Proposal".
initialContentNoOptional plain text to put in the new document. Use "\n" to separate paragraphs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • addedInput schema / properties / initialContent
      Added value: +{
+  "description": "Optional plain text to put in the new document. Use \"\\n\" to separate paragraphs.",
+  "maxLength": 1000000,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate a non-read-only, non-idempotent mutation, and the description adds context by disclosing the exact return values (documentId, title, URL) and the plain-text-only behavior. It does not fully discuss authentication prerequisites or side effects on Drive, but the description meaningfully expands on what the annotations alone provide.

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?

Three sentences carry the core create behavior, return values, formatting limitations, and sibling tool routing with no filler. The most important information is front-loaded, and each sentence earns its place.

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?

Despite having no output schema, the description discloses return values and the plain-text limitation, which are the main gaps an agent would need to know. It also covers what to use next for formatting and content additions, making it complete for a tool of this complexity.

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 coverage is 100%, so the schema already documents title and initialContent with examples and constraints. The description mentions 'given title' and 'initial plain text,' but these largely mirror the existing parameter descriptions rather than adding significant new meaning beyond the 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 starts with a specific verb and resource: 'Create a new Google Docs document with the given title in the user’s Google Drive,' and further specifies optional initial content. It clearly distinguishes this tool from siblings like append_text, copy_document, and delete_document by stating what it does and what it returns.

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 gives explicit routing guidance: it warns that formatting is not created from plain text and directs the agent to set_paragraph_style, format_text, or create_bulleted_list, plus find_text or get_document for indexes. It also explicitly says to use append_text for adding more content later, which is strong when-to-use-versus-alternatives guidance.

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