Skip to main content
Glama

docs insert text

docs_insert_text

Insert text at a specific index in a Google Docs document by supplying the document ID, text, and target index.

Instructions

Insert text at a specific document index.

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>",
      "index": "<index>"
    },
    "name": "docs_insert_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
indexYes
document_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond what those flags and the name already convey: it does not state that existing text shifts rather than being overwritten, or what happens on a repeated call or an out-of-range index.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with zero filler, so nothing is wasted. However, the brevity comes from under-specification rather than disciplined editing, leaving the agent without the details it needs.

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

Completeness2/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. But for a non-idempotent mutation with three fully undocumented parameters and two close siblings, the definition should at minimum clarify index semantics and how it differs from append/replace.

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 all three parameters rely on the description, which only echoes 'index' and 'text' without defining indexing base, units, valid range, or what document_id must refer to. The one semantic hint, that insertion is positional, is already implied by the tool name.

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?

A specific verb plus resource and position: 'Insert text at a specific document index.' An agent can tell what operation is performed, but nothing distinguishes it from sibling docs_append_text or docs_replace_text, so the agent must guess which of the three to use.

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?

There is no statement of when to use this instead of append or replace, no prerequisites (document write access, document must exist), and no exclusions. Usage is only implied by the word 'insert'.

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