Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

docs_insert_markdown

Append Markdown to the end of a Google Doc or insert it at a specific index to add content without rewriting the document.

Instructions

Append Markdown content to the end of a Doc, or insert it at a specific index (from docs_read structured).

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>",
      "markdown": "<markdown>"
    },
    "name": "docs_insert_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoOmit to append at the end
markdownYes
documentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds that insertion is additive (append or insert at an index) and where the index value originates, but it doesn't say whether existing content shifts, how Markdown is converted, or what happens on an invalid index.

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?

A single front-loaded sentence that covers both modes of operation with no filler. The parenthetical '(from docs_read structured)' is slightly terse but earns its place by pointing at the source of index values.

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?

For a three-parameter mutation tool with no output schema, the description covers the core action and the two modes well enough to invoke it. It leaves gaps around write permissions, error behavior for out-of-range indexes, and how the returned result (if any) can be used, which matters for a writer with openWorldHint=true.

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 only 33%: index is documented in the schema but markdown and documentId are not. The description compensates somewhat by explaining that index refers to a position obtained from docs_read structured output and that omitting it appends, but it says nothing about documentId format or markdown dialect/size limits.

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 pair (append/insert) and resource (Markdown content into a Doc), which clearly separates it from docs_insert_image and docs_insert_table. It stops short of naming the nearest alternative, docs_replace_text, so differentiation is implied rather than explicit.

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?

Useful implied guidance: the index comes from docs_read structured output, which tells the agent to call docs_read first. However, there is no explicit statement of when to prefer docs_replace_text or docs_batch_update, and no preconditions (e.g., document must exist or be writable) are given.

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