Skip to main content
Glama

docs append text

docs_append_text

Append text to the end of a Google Doc, with an optional named heading style, to add new content without rewriting existing sections.

Instructions

Append text to the end of a document, optionally as a named heading style.

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>",
      "text": "<text>"
    },
    "name": "docs_append_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
document_idYes
heading_styleNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description usefully clarifies that writing happens at the end, so existing content is preserved, but it does not surface the meaningful behavioral consequence of idempotentHint=false — repeated calls will duplicate the appended text — nor any permission or revision requirements.

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?

A single front-loaded sentence with zero filler; the operation and the optional variation are both stated immediately.

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?

An output schema exists, so return values need not be described, and the core write behavior is clear. However, for a non-idempotent mutation tool with 0% parameter documentation, the definition leaves the heading_style vocabulary and the duplicate-on-retry risk unexplained.

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%, so the description carries the full burden, and it only partially delivers. It clarifies that 'text' is appended and that 'heading_style' is optional and named, but gives no accepted style names/format, and says nothing about the expected form of 'document_id'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Append text to the end of a document') plus an optional modifier ('named heading style'). The word 'append' plus 'to the end' naturally distinguishes it from insert/replace siblings, though no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is for adding content at the tail of an existing document rather than inserting mid-document or replacing content. There is no explicit when-to-use/when-not guidance, no statement about whether the document must exist, and no mention of how it relates to docs_insert_text or docs_replace_text.

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