Skip to main content
Glama

resize_sheet_dimensions

Resize, auto-resize, freeze, hide/unhide, or insert/delete rows and columns in Google Sheets.

Instructions

Manages sheet-level dimension properties: resize columns/rows, auto-resize to fit content, freeze rows/columns, hide/unhide rows/columns, and insert/delete rows/columns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address. Required.
spreadsheet_idYesThe ID of the spreadsheet. Required.
sheet_nameNoSheet name to target. Defaults to the first sheet if not provided.
column_sizesNoDict mapping column letters to pixel widths. Example: {"A": 200, "C": 300}. Can be a JSON string or Python dict.
row_sizesNoDict mapping 1-based row numbers to pixel heights. Example: {"1": 40, "3": 60}. Can be a JSON string or Python dict.
auto_resize_columnsNoList of column letters to auto-resize to fit content. Example: ["A", "B"].
auto_resize_rowsNoList of 1-based row numbers to auto-resize to fit content. Example: [1, 2].
frozen_row_countNoNumber of rows to freeze from the top. Use 0 to unfreeze all rows.
frozen_column_countNoNumber of columns to freeze from the left. Use 0 to unfreeze all columns.
hide_columnsNoList of column letters to hide. Example: ["C", "D"].
unhide_columnsNoList of column letters to unhide. Example: ["C", "D"].
hide_rowsNoList of 1-based row numbers to hide. Example: [3, 4].
unhide_rowsNoList of 1-based row numbers to unhide. Example: [3, 4].
insert_rowsNoNumber of rows to insert.
insert_rows_atNo1-based row number to insert before. Appends to the end of the sheet if omitted.
insert_columnsNoNumber of columns to insert.
insert_columns_atNoColumn letter to insert before (e.g. "C"). Appends to the end if omitted.
delete_rowsNoList of 1-based row numbers to delete. Example: [5, 6].
delete_columnsNoList of column letters to delete. Example: ["E", "F"].

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries full burden but only lists actions without disclosing behavioral traits like write permissions, data shifting on insert/delete, or that freeze replaces existing settings. It lacks detail on side effects.

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 a single sentence but effectively front-loads the purpose. It is concise, though packing a list of operations makes it slightly dense.

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?

Given the tool has 19 parameters, the description is too high-level. It does not explain how parameters relate or typical usage patterns, leaving the agent without sufficient context despite the existence of an output schema.

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%, and parameter descriptions are detailed. The tool description adds little beyond listing categories; it does not enhance understanding beyond the schema.

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?

The description clearly states the tool manages sheet-level dimension properties and lists specific actions (resize, auto-resize, freeze, hide/unhide, insert/delete). It distinguishes from sibling tools like format_sheet_range or modify_sheet_values by focusing on dimensions.

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 guidance on when to use this tool versus alternatives, such as format_sheet_range for formatting or modify_sheet_values for data changes. No exclusions or prerequisites are mentioned.

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