Inserts one or more columns into a Google Sheets spreadsheet at a specified position, shifting existing columns to the right.
Insert columns at a specific position
| Name | Required | Description | Default |
|---|---|---|---|
| sheetId | Yes | The ID of the sheet | |
| endIndex | No | Ending column index (0-based) | |
| startIndex | Yes | Starting column index (0-based) | |
| spreadsheetId | Yes | The ID of the spreadsheet |
Changes observed during successful MCP inspections.
v2.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, and the description fails to mention side effects like shifting existing data, required permissions, or the number of columns inserted based on endIndex and startIndex.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence that immediately conveys the core action without unnecessary detail, making it highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks important context such as expected return value, error conditions, or the relationship between startIndex and endIndex, leaving gaps for effective use despite the clear purpose.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All four parameters have schema descriptions, providing basic meanings (e.g., '0-based' indexes), but the description does not add extra clarity about how endIndex and startIndex determine the insertion count or whether endIndex is optional.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Insert', the object 'columns', and the specific position, making it distinct from sibling tools like sheets_insert_rows and sheets_delete_columns.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to use this tool versus alternatives, such as when to insert rows or delete columns, nor any scenario-based context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.