Skip to main content
Glama

docs create document

docs_create_document

Create a Google Doc with a required title and optional initial text so AI agents can add new documents through a controlled write operation.

Instructions

Create a Google Doc with optional initial text. Write operation.

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_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
initial_textNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so "Write operation" merely restates structured data without adding value. Nothing is disclosed about where the doc lands, default sharing state, or whether repeated calls create duplicates, which matters given idempotentHint=false.

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?

Two short sentences, front-loaded with the core action. The trailing "Write operation" does not earn its place since annotations already say readOnlyHint=false.

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?

An output schema exists so return values needn't be described, and the tool is simple with two parameters. Still, for a non-idempotent, open-world create call, missing detail about destination location and duplicate behavior leaves an agent under-informed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden, yet it only mentions that initial text is optional. The title parameter is unexplained (is it required? used as filename?), and 'optional initial text' is essentially already conveyed by the schema's default:null and single required field.

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?

"Create a Google Doc with optional initial text" is a specific verb plus resource that clearly identifies a creation operation, and the sibling list shows other docs tools (docs_append_text, docs_insert_text) are different operations. It stops short of explicitly contrasting itself with those content-modification siblings, so a 4 rather than a 5.

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 guidance on when to use this versus docs_append_text or docs_insert_text, nor any prerequisites (auth/scopes, target drive or folder). The agent must infer the create-then-edit workflow on its own.

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