Skip to main content
Glama

resize_sheet_dimensions

Adjust Google Sheets layout by resizing columns and rows, auto-fitting content, freezing panes, hiding/unhiding elements, and inserting/deleting rows or columns.

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 provided, the description carries full burden but offers minimal behavioral insight. It lists operations but doesn't disclose critical traits: whether changes are destructive (deleting rows/columns permanently removes data), if there are rate limits, authentication requirements beyond the user_google_email parameter, or how conflicts between parameters are resolved (e.g., hiding and unhiding the same column).

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, well-structured sentence that efficiently lists all supported operations. It's front-loaded with the core purpose and avoids redundancy. However, it could be slightly more concise by grouping related operations (e.g., 'hide/unhide rows/columns' instead of listing them separately).

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 high parameter count (19) and mutation-heavy nature with no annotations, the description is incomplete. It lacks behavioral context (destructiveness, permissions), usage guidance, and output expectations (though an output schema exists). For a complex mutation tool, more context about side effects and constraints is needed despite the comprehensive parameter 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%, so the schema fully documents all 19 parameters. The description adds no parameter-specific semantics beyond the high-level operation list. It doesn't explain parameter interactions, defaults beyond what's in the schema, or provide examples of combined usage. Baseline 3 is appropriate when the schema does all the heavy lifting.

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 purpose with specific verbs ('manages sheet-level dimension properties') and lists concrete operations (resize columns/rows, auto-resize, freeze, hide/unhide, insert/delete). It distinguishes itself from sibling tools by focusing on sheet dimension manipulation rather than data validation, formatting, or other spreadsheet functions.

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. It doesn't mention prerequisites (e.g., needing edit permissions), constraints (e.g., maximum dimensions), or suggest other tools for related tasks like 'format_sheet_range' for styling or 'modify_sheet_values' for content changes.

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