google-workspace-mcp

docs_format_text

Format a text range in Google Docs by applying bold, italic, underline, font size, color, or strikethrough to selected indices.

Instructions

Apply formatting (bold, italic, underline, font size, color) to a text range in a Google Doc.

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>",
      "start_index": "<start_index>",
      "end_index": "<end_index>"
    },
    "name": "docs_format_text"
  }
}

Input Schema

Name	Required	Description	Default
`bold`	No
`italic`	No
`end_index`	Yes
`font_size`	No
`underline`	No
`document_id`	Yes
`start_index`	Yes
`strikethrough`	No
`foreground_color`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose mutation effects. It only says 'Apply formatting' without explaining that it modifies existing text, whether formatting is overwritten or merged, what happens with invalid indices, or that it requires an authenticated document. This is a significant lack of transparency for a mutating tool.

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 a single sentence that is front-loaded with the key action and scope. Every word is necessary, and there is no redundancy.

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?

Given 9 parameters and no annotations, the description is too sparse. It does not address parameter semantics beyond naming formatting types, nor does it provide usage context. The presence of an output schema covers return values, but the description remains incomplete for a tool of this complexity.

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?

The schema has 0% description coverage. The description identifies the formatting attributes (bold, italic, underline, font size, color) that correspond to parameters, but it omits strikethrough and does not explain the meaning of start_index/end_index (e.g., zero-based, exclusive end) or the color format. It adds some semantics but leaves critical parameter details ambiguous.

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 that this tool applies inline formatting (bold, italic, underline, font size, color) to a specified text range in a Google Doc. It distinguishes this from sibling tools like docs_set_paragraph_style (paragraph-level) and docs_set_alignment (alignment).

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 guidance on when to use this tool versus alternatives. It does not mention that this is for character-level formatting or that docs_batch_update might be more appropriate for multiple changes. No exclusions or prerequisites are stated.

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

Deploy Server