Skip to main content
Glama
dipseth

google-workspace-unlimited

Unified Sheet Range Formatter

format_sheet_range
Idempotent

Apply cell formatting, borders, conditional rules, merge, column width/row height, and freezing to a Google Sheets range in one request.

Instructions

Apply comprehensive formatting to a range in Google Sheets with multiple formatting options in a single request - unified formatting tool that replaces format_sheet_cells, update_sheet_borders, add_conditional_formatting, and merge_cells

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boldNo
italicNo
sheet_idYesThe sheet ID
font_sizeNo
row_heightNoHeight in pixels for rows in range
text_colorNo
top_borderNo
cell_formatNoDictionary with cell formatting options like: { "bold": True, "italic": False, "fontSize": 12, "textColor": {"red": 0.0, "green": 0.0, "blue": 0.0}, "backgroundColor": {"red": 1.0, "green": 1.0, "blue": 1.0}, "horizontalAlignment": "CENTER", "verticalAlignment": "MIDDLE", "numberFormat": {"type": "CURRENCY", "pattern": "$#,##0.00"}, "wrapStrategy": "WRAP" }
freeze_rowsNoNumber of rows to freeze from top
left_borderNo
border_colorNo
border_styleNoStyle of borders ("SOLID", "DASHED", "DOTTED", etc.)
column_widthNoWidth in pixels for columns in range
right_borderNo
apply_bordersNoWhether to apply borders
bottom_borderNo
range_end_colYesEnding column index (exclusive)
range_end_rowYesEnding row index (exclusive)
text_rotationNo
wrap_strategyNo
condition_typeNo
freeze_columnsNoNumber of columns to freeze from left
spreadsheet_idYesThe ID of the spreadsheet
condition_valueNo
range_start_colYesStarting column index (0-based)
range_start_rowYesStarting row index (0-based)
background_colorNo
border_positionsNoWhich borders to apply
conditional_rulesNoList of conditional formatting rules
user_google_emailNoThe user's Google email address for Sheets access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).
merge_cells_optionNoMerge type if merging cells
number_format_typeNo
vertical_alignmentNo
horizontal_alignmentNo
condition_format_boldNo
inner_vertical_borderNo
number_format_patternNo
condition_format_italicNo
inner_horizontal_borderNo
condition_format_text_colorNo
condition_format_background_colorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if operation failed
rangeYesCell range that was formatted
messageYesSuccess or error message
sheetIdYesSheet ID where formatting was applied
successYesWhether the formatting succeeded
spreadsheetIdYesUnique identifier for the spreadsheet
requestsAppliedYesNumber of formatting requests successfully applied
formattingDetailsYesDetails of all formatting applied
Behavior3/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the agent knows it's a safe write operation. The description adds minimal extra behavioral context beyond stating it's a unified tool.

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 concise and front-loaded with the core purpose. However, it could benefit from a structured list of formatting capabilities to improve scannability, given the tool's complexity.

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?

Given the tool's high complexity (41 parameters) and the presence of annotations and an output schema, the description is adequate but does not fully explain the scope of formatting options or edge cases. It could be more thorough.

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

Parameters2/5

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

With only 41% schema coverage, the description should compensate by explaining key parameters, but it does not detail any parameters beyond saying 'multiple formatting options.' The schema itself provides descriptions for some parameters, but the description adds no additional 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 applies comprehensive formatting to a range in Google Sheets with multiple options in a single request. It explicitly names the four predecessor tools it replaces, distinguishing it from siblings.

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

Usage Guidelines4/5

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

The description implies this tool is for unified formatting when multiple formatting options are needed, but it does not explicitly state when not to use it or mention alternatives like individual tools for simpler tasks.

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/dipseth/google_workspace_fastmcp2'

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