Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by risvan1605
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_google_doc

Automate creation of Google Docs with specified title and optional text content. Returns document ID and URL for immediate access.

Instructions

Create a new Google Document.

Args: title: The title of the new document. content: Optional initial text content to add to the document body.

Returns: Document ID, title, and URL on success, or error details on failure.

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

Input Schema

NameRequiredDescriptionDefault
titleYes
contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It does not disclose side effects, authentication needs, or behavior on duplicate titles. It only mentions return types, lacking depth for a mutation operation.

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 very concise with a clear Args and Returns structure. Every sentence adds value without redundancy.

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 (2 params, no output schema), the description adequately explains the return value (ID, title, URL) and parameter roles. However, it lacks error handling details or usage context for edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description explains both parameters: 'title' as the document title and 'content' as optional initial text. This adds meaning beyond the schema's type and required fields.

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 'Create a new Google Document,' which is a specific verb+resource pair, and it distinguishes from sibling tools like 'read_google_doc' and 'append_to_google_doc' by focusing on creation.

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?

No guidance on when to use this tool vs alternatives like 'append_to_google_doc' or 'draft_email'. The description lacks context on prerequisites or exclusions.

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