Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by VGdotcom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

append_content

Append text or notes to the end of an existing Google Document. Use this to add content or annotations without altering previous text.

Instructions

Append text or notes to the end of an existing Google Document.

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_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
formattingNo
document_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Conveys basic behavior (append to end) but no annotations provided. Missing details on permissions, limitations, or formatting handling. Adequate for a simple operation.

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?

Single sentence with no waste. Could be improved by front-loading the resource and action more explicitly.

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

Completeness3/5

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

Given no annotations and simple operation, description is adequate but missing usage context and parameter guidance. Output schema exists but doesn't compensate for missing explanation.

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

Parameters2/5

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

Schema description coverage is 0%; description only hints at 'content' parameter ('text or notes'). Does not explain 'document_id' or 'formatting' beyond their names.

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 verb 'Append' and resource 'Google Document', specifying 'text or notes' and 'to the end'. Distinct from sibling tools (draft_email, send_email) which are email-related.

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

Usage Guidelines2/5

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

No guidance on when to use or when not to use. Lacks alternatives or context for selection. Only describes the action itself.

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