Skip to main content
Glama
redesignhealth

Google Workspace MCP Server

format_sheet_range

Apply background and text colors, plus number or date formats, to a specific cell range in Google Sheets.

Instructions

Applies formatting to a range: background/text color and number/date formats.

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

Args: user_google_email (str): The user's Google email address. Required. spreadsheet_id (str): The ID of the spreadsheet. Required. range_name (str): A1-style range (optionally with sheet name). Required. background_color (Optional[str]): Hex background color (e.g., "#FFEECC"). text_color (Optional[str]): Hex text color (e.g., "#000000"). number_format_type (Optional[str]): Sheets number format type (e.g., "DATE"). number_format_pattern (Optional[str]): Optional custom pattern for the number format.

Returns: str: Confirmation of the applied formatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
range_nameYes
text_colorNo
spreadsheet_idYes
background_colorNo
user_google_emailYes
number_format_typeNo
number_format_patternNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the transparency burden. It usefully discloses value constraints (hex colors, Sheets format types) and default sheet behavior, but does not explicitly state that this is a mutating operation that may overwrite existing formatting, nor does it mention permissions or error behavior.

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 well-structured with a concise summary followed by an Args/Returns breakdown. Every sentence adds useful information, and there is no filler or unnecessary repetition.

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?

The description covers all parameters, return value, accepted value examples, and default sheet behavior. It is missing a few details such as whether unspecified format properties are preserved or cleared and possible error conditions, but it is largely complete for a formatting tool.

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?

Schema description coverage is 0%, but the Args section fully documents all seven parameters, including required status, types, examples, and defaults. This fully compensates for the schema gap and adds significant semantic meaning.

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 the tool's function with a specific verb ('Applies formatting') and resource ('a range'), and lists the exact formatting dimensions (background/text color and number/date formats). This differentiates it from sibling tools like modify_sheet_values and conditional formatting tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives context such as default first-sheet behavior and accepted number format values, but it does not explicitly say when to use this tool over alternatives like add_conditional_formatting or modify_sheet_values. Usage is implied rather than explicitly contrasted with siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/redesignhealth/google-mcp-unofficial'

If you have feedback or need assistance with the MCP directory API, please join our Discord server