Skip to main content
Glama
Sign In
gg-mcp

gg-mcp

by tannht
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_document

Create a new Google Docs document and optionally insert initial text to streamline drafting.

Instructions

Create a new Google Docs document with optional initial 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": "create_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
body_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects (e.g., where the document is saved), required permissions, error handling, or quotas. The agent is left unaware of important behavioral traits beyond the basic creation action.

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?

The description is a single, front-loaded sentence of 9 words—efficient and to the point. However, it omits important information like return value or usage context, making it slightly too brief for full clarity.

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

Completeness2/5

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

Given no output schema and no annotations, the description lacks completeness: it does not specify the return value (e.g., document ID or URL), error cases, or operational behavior like default creation location. For a simple creation tool, the description is minimal but misses elements essential for effective agent use.

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 add meaning. It clarifies that body_text is optional and its role as initial content, but the title parameter is only described by its name. The description partially compensates but does not fully explain the parameters' expected values or constraints.

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 clearly identifies the tool's action ('Create a new Google Docs document') and specifies 'with optional initial text,' distinguishing it from sibling tools like create_spreadsheet or create_presentation. However, it does not explicitly differentiate from append_to_document, which is a related but distinct operation.

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?

The description provides no guidance on when to use this tool versus alternatives such as append_to_document or create_presentation. There are no usage conditions, prerequisites, or explicit when/not-to-use instructions.

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