Google Sheets Advanced MCP Server

Overview Schema Source Related Servers Discussions Admin

sheets_add_conditional_formatting

Idempotent

Add conditional formatting rules to a spreadsheet range to highlight cells that meet criteria like greater than, less than, or text contains.

Instructions

Adds a conditional formatting rule to a range in a spreadsheet

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>",
      "range": "<range>",
      "rule_type": "<rule_type>"
    },
    "name": "sheets_add_conditional_formatting"
  }
}

Input Schema

Name	Required	Description
`range`	Yes	The A1 notation range to apply formatting to
`format`	No	Cell format to apply when condition is met
`values`	No	Condition values (e.g. threshold numbers, text to match, formula)
`rule_type`	Yes	The type of conditional formatting rule
`color_scale`	No	Color scale configuration (only used when rule_type is color_scale)
`spreadsheet_id`	Yes	The ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare this is a non-destructive mutation (readOnlyHint=false, destructiveHint=false) that is idempotent. The description adds nothing beyond that: it doesn't say whether rules accumulate on a range, whether they can be overwritten or removed, or what permissions are needed.

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?

A single clean sentence with the verb and resource front-loaded and no wasted words. It is efficient, though arguably too terse to be fully useful.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation tool with nested objects and no output schema, the full schema and annotations cover structural needs, but the description leaves behavioral questions open (rule accumulation, interaction with existing rules, effect on the target range).

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including the nested format and color_scale objects is documented in the schema itself. The description adds no parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb (adds) and resource (conditional formatting rule) scoped to a range in a spreadsheet. The term 'conditional formatting' is distinct enough from siblings like sheets_format_cells or sheets_set_data_validation, though the description never explicitly contrasts itself with them.

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?

No guidance on when to use this tool versus sheets_format_cells (static formatting) or sheets_set_data_validation. No prerequisites, no mention of what happens when a rule already exists on the range.

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