Skip to main content
Glama

Modify Doc Text

modify_doc_text
Destructive

Insert, replace, or format text in a Google Doc with a single operation, applying bold, italic, font, color, links, and more.

Instructions

Modifies text in a Google Doc - can insert/replace text and/or apply formatting in a single operation.

TIP: To append text to the end of the document without calculating indices, set end_of_segment=true. This avoids index calculation errors.

For ordinary header/footer text, prefer update_doc_headers_footers. Only pass segment_id when you already have a real header/footer/footnote segment ID from inspect_doc_structure output. Do not guess IDs such as "kix.header" or "kix.footer".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesUser's Google email address
document_idYesID of the document to update
start_indexYesStart position for operation using Docs API indices from inspect_doc_structure. For the main body, 0 is also accepted as an alias for the first writable position.
end_indexNoEnd position for text replacement/formatting (if not provided with text, text is inserted)
textNoNew text to insert or replace with (optional - can format existing text without changing it)
tab_idNoOptional document tab ID to target
segment_idNoOptional header/footer/footnote segment ID to target
end_of_segmentNoInsert text at the end of the targeted segment instead of start_index
boldNoWhether to make text bold (True/False/None to leave unchanged)
italicNoWhether to make text italic (True/False/None to leave unchanged)
underlineNoWhether to underline text (True/False/None to leave unchanged)
strikethroughNoWhether to strike through text (True/False/None to leave unchanged)
font_sizeNoFont size in points
font_familyNoFont family name (e.g., "Arial", "Times New Roman")
font_weightNoFont weight (100-900 in steps of 100; requires font_family)
text_colorNoForeground text color (#RRGGBB)
background_colorNoBackground/highlight color (#RRGGBB)
link_urlNoHyperlink URL (http/https)
clear_linkNoRemove hyperlink from the target range
baseline_offsetNoOne of NONE, SUPERSCRIPT, SUBSCRIPT
small_capsNoWhether to apply small caps

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context: the operation can both change text and apply formatting in one call, explains index behavior (start_index accepts 0 as alias), and warns against guessing segment IDs. No contradiction with annotations.

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?

The description is concise with three short paragraphs: purpose, a tip for efficient usage, and a warning about segment_id. Every sentence adds value without unnecessary detail. Front-loaded with the core 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?

With 21 parameters and an output schema, the description covers essential usage patterns, common pitfalls (index errors), and cross-references sibling tools. It doesn't explain the return value, but the output schema handles that. Could mention auth prerequisites, but overall complete for typical use.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema: clarifies that start_index can be 0 for the first writable position, end_of_segment avoids index calculation, and segment_id must come from inspect_doc_structure. It also clarifies how end_index and text interact (insert vs replace).

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?

The description clearly states the tool modifies text in a Google Doc with two core capabilities (insert/replace text and apply formatting). It distinguishes from the sibling tool update_doc_headers_footers by advising that tool for ordinary header/footer text, and highlights the append behavior via end_of_segment.

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

Usage Guidelines5/5

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

The description provides explicit guidance: when to use end_of_segment to avoid index errors, to prefer update_doc_headers_footers for headers/footers, and to only pass segment_id from inspect_doc_structure output, not guessed IDs. This helps the agent choose appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chadvdwww-hash/worksuite-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server