Skip to main content
Glama

format_sheet_range

Apply formatting to a spreadsheet range, including colors, number formats, text wrapping, alignment, and bold/italic styling.

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
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address. Required.
spreadsheet_idYesThe ID of the spreadsheet. Required.
range_nameYesA1-style range (optionally with sheet name). Required.
background_colorNoHex background color (e.g., "#FFEECC").
text_colorNoHex text color (e.g., "#000000").
number_format_typeNoSheets number format type (e.g., "DATE").
number_format_patternNoCustom pattern for the number format.
wrap_strategyNoText wrap strategy - WRAP (wrap text within cell), CLIP (clip text at cell boundary), or OVERFLOW_CELL (allow text to overflow into adjacent empty cells).
horizontal_alignmentNoHorizontal text alignment - LEFT, CENTER, or RIGHT.
vertical_alignmentNoVertical text alignment - TOP, MIDDLE, or BOTTOM.
boldNoWhether to apply bold formatting.
italicNoWhether to apply italic formatting.
font_sizeNoFont size in points.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discusses color formats and number format types, but does not disclose key behavioral traits: whether formatting is incremental or resets unset properties, if the operation is reversible, or any permission/rate-limit requirements. This is insufficient for a formatting tool with 13 parameters.

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 extremely concise: three sentences, no filler. It is front-loaded with the main purpose, then provides format-specific details, and ends with a practical usage note. Every sentence earns its place.

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

Completeness2/5

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

Despite having an output schema (not shown) and 13 parameters, the description lacks completeness. It does not explain interaction of multiple formatting properties, whether the operation is an update or replacement, or error scenarios. For a complex tool, more context is needed to ensure correct use.

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 baseline is 3. The description adds value beyond schema: it clarifies that colors accept hex strings (#RRGGBB) and that number formats follow Sheets types (e.g., NUMBER, CURRENCY, DATE, PERCENT). It also notes the sheet name behavior for range_name. This enhances parameter understanding.

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 it applies formatting to a range, listing specific categories (colors, number formats, text wrapping, alignment, text styling). It is a specific verb+resource that distinguishes this tool from siblings (which operate on other Google Workspace entities like Docs or Slides).

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 provides implicit usage context (e.g., 'If no sheet name is provided, the first sheet is used') but does not explicitly state when to use this tool versus alternatives like 'modify_sheet_values' or 'manage_conditional_formatting'. No exclusions or alternative tool references are given.

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/HuntsDesk/ve-gws'

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