Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

docs_create

Create a Google Doc with optional Markdown content and save it to a specified Drive folder.

Instructions

Create a Google Doc, optionally with Markdown content (headings, bold/italic, links, bullet & numbered lists, code) and in a given Drive folder.

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
titleYes
folderIdNo
markdownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context by enumerating the Markdown subset that will be interpreted (headings, bold/italic, links, lists, code), which no structured field conveys, but it says nothing about required scopes, whether an existing doc with the same title is affected, or what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the operation stated first and qualifiers after. The parenthetical syntax list is somewhat long but carries real information about accepted input, so it earns its space.

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

Completeness3/5

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

There is no output schema, so the description should say what a successful create yields (a new document ID or URL), which matters for chaining into docs_batch_update or docs_insert_markdown. Combined with the undocumented title parameter and unspecified default folder behavior, the definition is adequate but leaves meaningful gaps.

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 usefully clarifies that markdown is a formatted-content payload with a specific supported syntax and that folderId designates the destination Drive folder, but it leaves the required title parameter unexplained and does not state what happens when folderId is omitted (root vs. default location).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Create a Google Doc") plus scope details (optional Markdown content, target Drive folder). It does not explicitly contrast itself with siblings like docs_insert_markdown, so an agent must infer that this one creates a new document rather than modifying an existing one.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The phrase "optionally with Markdown content" hints at the create-vs-insert distinction, but an agent gets no stated rule for choosing between docs_create, docs_insert_markdown, or drive_copy.

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