Skip to main content
Glama
ammarqaisar11a55

Google Docs MCP

by ammarqaisar11a55
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

Append text to Google Doc

append_text

Append text to the end of a Google Doc without indexes. Returns insertion length and index range for formatting.

Instructions

Append text to the end of a Google Doc’s body. No indexes are needed, so prefer this over insert_text whenever content should go at the end. By default the text starts in a new paragraph (a paragraph break is added first if the last paragraph is not empty); set startNewParagraph=false to continue the last paragraph instead. Use "\n" inside text to create further paragraphs. Returns insertedLength and the index range of the appended text (textStartIndex/textEndIndex), which can be passed to format_text or set_paragraph_style. Carriage returns become "\n" and control characters Google Docs cannot store are removed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to append. "\n" starts a new paragraph.
documentIdYesThe Google Docs document ID (the part between /d/ and /edit in the document URL). A full Google Docs URL is also accepted.
startNewParagraphNoStart the text in a new paragraph when the last paragraph is not empty (default true). Set false to continue the last paragraph.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover the safety profile (non-read-only, non-idempotent, non-destructive). The description goes well beyond, disclosing the default new-paragraph behavior and the conditional paragraph break, text normalization (carriage returns to \n, control-character stripping), and the appended index range usable downstream.

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?

Purpose is front-loaded in the first sentence, then routing, defaults, return values, and normalization each earn their sentence. Dense but zero waste.

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

Completeness5/5

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

No output schema exists, yet the description documents what is returned (insertedLength, textStartIndex/textEndIndex) and how to consume it, and covers the mutation's edge cases. Nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds real meaning the schema does not, notably how startNewParagraph interacts with a non-empty last paragraph and the role of \n in creating further paragraphs.

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+resource+scope (append text to the end of a Google Doc's body) and explicitly contrasts with the sibling insert_text. An agent can distinguish it from insert_text and format_text without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative and the selecting condition: 'prefer this over insert_text whenever content should go at the end.' No prerequisite/authentication guidance, but the routing guidance is unambiguous.

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

Install Server

Other Tools