Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by risvan1605
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

append_to_google_doc

Append text to the end of a Google Document using its document ID, adding content without overwriting existing text.

Instructions

Append content to the end of an existing Google Document.

The content is added after the existing text without overwriting anything.

Args: document_id: The ID of the Google Document to append to. content: The text content to append to the document.

Returns: Document ID, title, number of characters appended, and URL.

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": "append_to_google_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Discloses that content is added without overwriting and lists return values. With no annotations, the description carries full burden; it adequately describes the mutation behavior but lacks details on auth, rate limits, or error conditions.

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?

Concise with a clear main sentence, then sections for behavior, args, and returns. No fluff, front-loaded purpose.

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?

Given no output schema, description includes return values. Covers core behavior and parameters. Could mention error scenarios or permissions, but overall adequate for a simple append tool.

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 0%, so description compensates minimally. It explains document_id as the ID and content as text, but no additional details like format, length limits, or constraints. This is basic, not rich.

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?

Clearly states 'Append content to the end of an existing Google Document.' The verb 'append' and resource are specific, and the action is distinct from siblings like create_google_doc and read_google_doc.

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

Usage Guidelines3/5

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

Implied usage: use when you want to append to an existing doc. No explicit guidance on when not to use or compare with alternatives. The sibling list provides context but no direct exclusions.

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