Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Resize Sheet Dimensions

resize_sheet_dimensions

Destructive

Adjust row and column dimensions in Google Sheets: resize, auto-fit, freeze, hide, unhide, and insert or delete rows and 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

Name	Required	Description
`hide_rows`	No	List of 1-based row numbers to hide. Example: [3, 4].
`row_sizes`	No	Dict mapping 1-based row numbers to pixel heights. Example: {"1": 40, "3": 60}. Can be a JSON string or Python dict.
`sheet_name`	No	Sheet name to target. Defaults to the first sheet if not provided.
`delete_rows`	No	List of 1-based row numbers to delete. Example: [5, 6]. Best for non-contiguous rows.
`insert_rows`	No	Number of rows to insert.
`unhide_rows`	No	List of 1-based row numbers to unhide. Example: [3, 4].
`column_sizes`	No	Dict mapping column letters to pixel widths. Example: {"A": 200, "C": 300}. Can be a JSON string or Python dict.
`hide_columns`	No	List of column letters to hide. Example: ["C", "D"].
`delete_columns`	No	List of column letters to delete. Example: ["E", "F"].
`insert_columns`	No	Number of columns to insert.
`insert_rows_at`	No	1-based row number to insert before. Appends to the end of the sheet if omitted.
`spreadsheet_id`	Yes	The ID of the spreadsheet. Required.
`unhide_columns`	No	List of column letters to unhide. Example: ["C", "D"].
`auto_resize_rows`	No	List of 1-based row numbers to auto-resize to fit content. Example: [1, 2].
`delete_row_range`	No	Contiguous range of rows to delete, as "start:end" (1-based, inclusive). Example: "5:10" deletes rows 5 through 10. More efficient than delete_rows for large contiguous ranges.
`frozen_row_count`	No	Number of rows to freeze from the top. Use 0 to unfreeze all rows.
`insert_columns_at`	No	Column letter to insert before (e.g. "C"). Appends to the end if omitted.
`user_google_email`	Yes	The user's Google email address. Required.
`auto_resize_columns`	No	List of column letters to auto-resize to fit content. Example: ["A", "B"].
`frozen_column_count`	No	Number of columns to freeze from the left. Use 0 to unfreeze all columns.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedv1.28.0Sep 24, 2026

changedInput schema / properties / auto_resize_columns / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

changedInput schema / properties / auto_resize_rows / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  }
+]

changedInput schema / properties / column_sizes / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]

changedInput schema / properties / delete_columns / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / delete_row_range / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / delete_row_range / type
```
Added value: +"string"
```

changedInput schema / properties / delete_rows / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / frozen_column_count / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / frozen_column_count / type
```
Added value: +"integer"
```

removedInput schema / properties / frozen_row_count / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / frozen_row_count / type
```
Added value: +"integer"
```

changedInput schema / properties / hide_columns / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

changedInput schema / properties / hide_rows / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / insert_columns / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / insert_columns / type
```
Added value: +"integer"
```

removedInput schema / properties / insert_columns_at / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / insert_columns_at / type
```
Added value: +"string"
```

removedInput schema / properties / insert_rows / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / insert_rows / type
```
Added value: +"integer"
```

removedInput schema / properties / insert_rows_at / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / insert_rows_at / type
```
Added value: +"integer"
```

changedInput schema / properties / row_sizes / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]

removedInput schema / properties / sheet_name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / sheet_name / type
```
Added value: +"string"
```

changedInput schema / properties / unhide_columns / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

changedInput schema / properties / unhide_rows / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "integer"
+    },
+    "type": "array"
+  }
+]

Addedv1.0.1Jul 31, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false Mkdocs. The description adds a list of operations but does not disclose important behavioral consequences such as irreversible deletion, reference shifts after row/column deletion, or whether combinations of operations are applied atomically. With destructiveHint already present, the description earns little additional transparency credit.

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?

One clean, front-loaded sentence that summarizes the tool's scope with a colon-delimited list of operation families. There is no fluff, repetition, or irrelevant detail. It efficiently tells an agent what the tool can do in a single glance.

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 has 20 parameters, multiple independent operation families (resize, freeze, hide, insert, delete), and an output schema, the description is adequate for initial selection but not for safe invocation. It does not explain parameter grouping, mutual exclusivity, or edge cases like delete_rows vs. delete_row_range, despite those details living partly in schema descriptions. The overall context is present but not complete enough for a complex tool.

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 input schema already documents all 20 parameters in detail. The description adds only a high-level category list and no parameter-specific meaning. Baseline 3 applies because the schema carries the full burden of parameter documentation.

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 names a specific resource ('sheet-level dimension properties') and enumerates the concrete operations it supports ('resize columns/rows, auto-resize..., freeze..., hide/unhide..., insert/delete...'). This is clearer than a vague 'manages sheets' but the verb 'manages' is broad, and it does not explicitly distinguish itself from sibling tools like format_sheet_range or manage_sheet_tab.

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 strongly implies when to use the tool: whenever an agent needs to alter row/column dimensions, freezing, hiding, or insertion/deletion. However, it gives no explicit exclusions or comparisons to alternatives such as format_sheet_range or modify_sheet_values, so an agent must infer the boundary between this tool and similar spreadsheet tools.

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

Deploy Server