mcp-google-sheets

set_tab_color

Destructive

Change the color of a sheet tab in Google Sheets using a hex color code. Specify the spreadsheet, sheet, and color to update the tab visually.

Instructions

Change the color of a sheet tab.

Args: spreadsheet_id: The ID of the spreadsheet sheet: Sheet/tab name color: Hex color (e.g., '#FF0000' for red, '#00FF00' for green). Use '#FFFFFF' or 'none' to remove color.

Returns: Result of the color change 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>",
      "color": "<color>"
    },
    "name": "set_tab_color"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes
`sheet`	Yes
`color`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 21, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotation destructiveHint=true is present, but the description does not elaborate on what 'destructive' means for a tab color change. It also does not disclose any additional behavioral traits such as side effects, authorization needs, or rate limits. The description adds the hex format guidance but lacks depth beyond that.

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 very concise: one line for purpose, then a clear Args section, and a Returns line. Every part serves a purpose with no redundant or extraneous information. It is well-organized and front-loaded.

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 simple tool with three parameters and an output schema, the description covers the essential usage (color format, special values). It does not mention that spreadsheet_id must be a valid ID or that sheet must exist, but the output schema exists to clarify return values. Overall, it is nearly complete with only minor gaps.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description fully compensates by explaining all three parameters. For 'color', it provides concrete examples (e.g., '#FF0000') and special values ('#FFFFFF' or 'none'). This adds significant meaning beyond the bare schema types.

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 states 'Change the color of a sheet tab,' which is a specific verb and resource. This clearly distinguishes the tool from siblings like rename_sheet or move_sheet, which perform different actions.

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 explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts, or situations where another sibling tool would be more appropriate. Usage is only implied by the action name.

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