Skip to main content
Glama
FallenOne1701

Google Workspace MCP Server

by FallenOne1701
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Append to Google Doc

google_docs_append_content

Append text to an existing Google Doc using only document ID and content. Add updates or notes without calculating Docs insertion indexes.

Instructions

Append plain text to the end of an existing Google Doc.

When to use:

  • Add content to a known document without calculating Google Docs insertion indexes.

  • Pass the document ID only (not a full Docs URL).

Required parameters: document_id, content (non-empty). Optional: add_newline_before (default true), add_newline_after (default false).

Side effects: Mutates the document body by inserting text at the end of the body segment. Uses revision WriteControl so concurrent edits are detected rather than applied blindly.

Success: Returns document_id, appended_characters, and provider "google_docs". Common failures: VALIDATION_ERROR (empty content), RESOURCE_NOT_FOUND, AUTHENTICATION_REQUIRED, AUTHORIZATION_DENIED, GOOGLE_API_ERROR (including stale revision).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesRequired. Non-empty text to append to the document body.
document_idYesRequired. Google Docs document ID (not the full URL).
add_newline_afterNoWhen true, ensure appended content ends with a newline. Defaults to false.
add_newline_beforeNoWhen true, ensure appended content starts on a new line. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag non-readOnly, non-idempotent, openWorld, non-destructive. Description adds valuable context beyond annotations: body mutation via end insertion, revision WriteControl for concurrency detection, and a concrete failure taxonomy with stale revision. Missing detail on exact return timing or rate limits, but strong coverage.

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?

Front-loaded first sentence states the action, followed by structured sections (When to use, Required, Optional, Side effects, Success, Failures). Every sentence adds value with no 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?

Covers purpose, usage, side effects, return fields, and failure modes, which is substantial for a 4-param mutation tool with no output schema. Slightly limited on edge cases like document size limits or content formatting constraints, but overall quite complete.

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 coverage is 100% with descriptions, defaults, and minLength constraints all present. Description restates required/optional params and defaults, adding little beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb (Append), resource (plain text), and target (end of an existing Google Doc). Distinguishes the operation from siblings (gmail tools) by scope and clarifies 'plain text' specificity.

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?

Explicit 'When to use' section: adding content without calculating insertion indexes, and passing document ID only (not URL). No explicit when-not-to-use or named alternative, but context is clear enough to guide invocation.

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