Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Format Sheet Range

format_sheet_range

Apply colors, number formats, alignment, wrapping, and text styling to a Google Sheets range. Specify hex colors, number types, and font options for precise cell formatting.

Instructions

Applies formatting to a range: colors, number formats, text wrapping, alignment, and text styling.

Colors accept hex strings (#RRGGBB). Number formats follow Sheets types (e.g., NUMBER, CURRENCY, DATE, PERCENT). If no sheet name is provided, the first sheet is used.

Input Schema

TableJSON Schema

Name	Required	Description
`bold`	No	Whether to apply bold formatting.
`italic`	No	Whether to apply italic formatting.
`font_size`	No	Font size in points.
`range_name`	Yes	A1-style range (optionally with sheet name). Required.
`text_color`	No	Hex text color (e.g., "#000000").
`wrap_strategy`	No	Text wrap strategy - WRAP (wrap text within cell), CLIP (clip text at cell boundary), or OVERFLOW_CELL (allow text to overflow into adjacent empty cells).
`spreadsheet_id`	Yes	The ID of the spreadsheet. Required.
`background_color`	No	Hex background color (e.g., "#FFEECC").
`user_google_email`	Yes	The user's Google email address. Required.
`number_format_type`	No	Sheets number format type (e.g., "DATE").
`vertical_alignment`	No	Vertical text alignment - TOP, MIDDLE, or BOTTOM.
`horizontal_alignment`	No	Horizontal text alignment - LEFT, CENTER, or RIGHT.
`number_format_pattern`	No	Custom pattern for the number format.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / background_color / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / background_color / type
```
Added value: +"string"
```
- removedInput schema / properties / bold / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / bold / type
```
Added value: +"boolean"
```
- removedInput schema / properties / font_size / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / font_size / type
```
Added value: +"integer"
```
- removedInput schema / properties / horizontal_alignment / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / horizontal_alignment / type
```
Added value: +"string"
```
- removedInput schema / properties / italic / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / italic / type
```
Added value: +"boolean"
```
- removedInput schema / properties / number_format_pattern / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / number_format_pattern / type
```
Added value: +"string"
```
- removedInput schema / properties / number_format_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / number_format_type / type
```
Added value: +"string"
```
- removedInput schema / properties / text_color / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / text_color / type
```
Added value: +"string"
```
- removedInput schema / properties / vertical_alignment / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / vertical_alignment / type
```
Added value: +"string"
```
- removedInput schema / properties / wrap_strategy / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / wrap_strategy / type
```
Added value: +"string"
```
Addedv1.0.1Jul 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already convey that this is a non-read-only, non-destructive, non-idempotent operation. The description adds useful behavioral context beyond annotations: colors must be hex strings, number formats follow Sheets types, and the first sheet is used when no sheet name is given. However, it does not disclose whether unspecified formatting properties are preserved, cleared, or merged with existing formatting.

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 three sentences with no filler. The core purpose is front-loaded, and the constraint notes about colors, number formats, and default sheet are each meaningful and separated cleanly.

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?

For a 13-parameter tool, the fully described schema plus the added constraints on color, number-format values, and default sheet cover most invocation needs, and an output schema exists so return values need no explanation. The main missing piece is a statement about how formatting interacts with existing cell styles.

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 description coverage is 100%, so the baseline is 3. The description adds value by constraining color values to hex strings, listing Sheets number-format types such as NUMBER and CURRENCY, and clarifying the sheet-selection default. This goes beyond the schema's individual parameter descriptions without duplicating them.

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?

The description states a specific operation—'Applies formatting to a range'—and enumerates the style categories involved: colors, number formats, text wrapping, alignment, and text styling. It is clear and resource-specific, though it does not explicitly call out spreadsheet siblings such as manage_conditional_formatting or modify_sheet_values to reinforce the distinction.

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 about when to choose this tool instead of related siblings like modify_sheet_values or manage_conditional_formatting. The only operational note is the first-sheet default, which clarifies behavior but does not help with tool selection.

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

Deploy Server