Skip to main content
Glama
Sign In
MCP Google Workspace Server

MCP Google Workspace Server

by Daminigit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

google_docs_append_content

Append plain text to the end of a Google Doc without modifying existing content.

Instructions

Appends plain text content to the end of an existing Google Document. Use this tool to add new content at the bottom of a Google Doc without modifying existing content. The document ID can be found in the Google Doc URL: docs.google.com/document/d/<DOCUMENT_ID>/edit Existing document content is never overwritten or deleted.

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": {
      "document_id": "<document_id>",
      "content": "<content>"
    },
    "name": "google_docs_append_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe plain text content to append at the end of the document (required).
document_idYesThe Google Document ID from the document URL (required). Example: "1AbCdEfGhIjKlMnOpQrStUvWxYz"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It prominently states that existing content is never overwritten or deleted and that only plain text is appended, which are the key behavioral guarantees an agent needs. It does not cover failure modes or permissions, but the main non-destructive trait is well disclosed.

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 short and front-loaded with the core action. There is minor redundancy between 'without modifying existing content' and 'never overwritten or deleted,' but overall every sentence earns its place.

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?

For a simple two-parameter append operation with no output schema, the description covers the core semantics, the non-destructive behavior, and how to locate the required document ID. It could mention access requirements or behavior on nonexistent documents, but the essential information for correct use is present.

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 100%, so the schema already fully documents both parameters. The description adds a helpful hint about finding the document ID in the URL, but that information is also implied by the schema example, so it provides only marginal added value.

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 the specific action: appending plain text to the end of an existing Google Document. It makes the scope obvious and is easily distinguishable from the unrelated gmail sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use the tool ('add new content at the bottom of a Google Doc') and clarifies that existing content is preserved. It does not name alternatives, but the siblings are unrelated to Docs, so no exclusion is necessary.

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