mcp-google-sheets

format_cells

Destructive

Apply formatting to a range of cells in Google Sheets. Set bold, italic, font size, font color, background color, number format, and alignment.

Instructions

Apply formatting to a range of cells.

Args: spreadsheet_id: The ID of the spreadsheet sheet: Sheet/tab name range: A1 notation range (e.g., 'A1:C10') bold: Make text bold italic: Make text italic font_size: Font size in pt font_color: Hex color for text (e.g., '#FF0000') background_color: Hex color for cell background (e.g., '#FFFF00') number_format: Number format pattern (e.g., '#,##0.00', '0%', 'yyyy-mm-dd') horizontal_alignment: 'LEFT', 'CENTER', or 'RIGHT'

Returns: Result of the formatting operation

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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "sheet": "<sheet>",
      "range": "<range>"
    },
    "name": "format_cells"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes
`sheet`	Yes
`range`	Yes
`bold`	No
`italic`	No
`font_size`	No
`font_color`	No
`background_color`	No
`number_format`	No
`horizontal_alignment`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 21, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations set destructiveHint: true, but the description does not elaborate on destructive behavior (e.g., overwriting existing formatting). It adds minimal behavioral context beyond what annotations already provide.

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?

The description is well-structured with a clear one-liner and a parameter list. It is concise but the Args block adds necessary detail. No redundant sentences.

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?

Given the tool's complexity (10 params, destructive hint, output schema exists), the description covers most aspects. It explains all parameters but could mention behavior on omitted optionals or cumulative effects.

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?

With 0% schema description coverage, the description compensates by adding examples for number_format, font_color, and background_color. However, some parameters (e.g., bold, italic) lack examples, keeping it from a top score.

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 'Apply formatting to a range of cells' with a specific verb and resource. It distinguishes from siblings like 'add_conditional_format' or 'batch_update_cells' by listing many specific formatting options.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'add_conditional_format' for conditional rules). It does not mention any prerequisites or limitations.

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