Generic Gmail & Google Docs MCP Server

append_to_google_doc

Append text to the end of an existing Google Doc using its document ID and content. Markdown is not rendered.

Instructions

Append caller-supplied text to the end of an existing Google Doc. Does not create a document, generate content, or interpret markdown. Requires documentId and content.

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": {
      "documentId": "<documentId>",
      "content": "<content>"
    },
    "name": "append_to_google_doc"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes	Text to append at the end of the document. Written as supplied; markdown is not rendered.
`documentId`	Yes	Google Doc id from the document URL (the long id after /d/).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the operation is purely additive, takes text verbatim, and does not render markdown, but says nothing about required Google OAuth scopes, behavior on an invalid or missing documentId, or whether concurrent edits are safe — meaningful gaps for a write 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?

Three short sentences, front-loaded with the core action and followed immediately by the exclusions. Every clause earns its place; nothing is padding.

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 two-parameter append tool with no output schema and no annotations, the description covers the action, its scope limits, and its input requirements. Remaining omissions (auth prerequisites, error behavior, return shape) are minor at this complexity level.

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 both parameters are already fully documented, including the documentId format and the markdown caveat. The description only restates the required parameter names, adding no meaning beyond the schema — the baseline 3 applies.

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) and resource (text to the end of an existing Google Doc) with explicit scope. It also preempts three likely misreadings — document creation, content generation, and markdown interpretation — so an agent can tell exactly what this does and does not do.

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?

The 'Does not create a document, generate content, or interpret markdown' clause gives clear when-not guidance, which is the useful boundary here. It stops short of naming any alternative tool to use for those excluded cases, so it is not a full when/when-not/alternatives statement.

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

Deploy Server