Skip to main content
Glama

insert_columns

Insert columns before a specified start index in a Google Sheet, using zero-based half-open indices.

Instructions

Insert columns before start_index; indices are zero-based and half-open.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetYes
end_indexYes
start_indexYes
spreadsheet_idYes
inherit_from_beforeNo
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It explains the indexing but omits important details like whether existing data shifts, what happens to formulas or formatting, and whether the operation is destructive. The effect of the 'end_index' parameter on the insertion is unclear.

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 that directly conveys the core purpose and indexing detail. It is concise and front-loaded, but could be more structured by listing parameters or adding context.

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 5 parameters (4 required) and no output schema or annotations, the description is insufficient. It does not explain the return value, the effect of 'end_index', or the 'inherit_from_before' parameter, leaving the agent uncertain about how to invoke the tool correctly.

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 0%, so the description must compensate. It explains the 'start_index' parameter's zero-based half-open semantics but fails to describe 'end_index' (likely the number of columns to insert) or 'inherit_from_before'. The addition is partial but helpful.

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 action ('Insert columns') and the location ('before start_index'), and explains the zero-based half-open indexing. However, it does not distinguish this tool from sibling tools like 'append_columns_to_sheet' or 'delete_columns', which could cause confusion.

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?

No guidance is provided on when to use this tool versus alternatives such as 'append_columns_to_sheet' or 'insert_rows'. The description lacks any context about prerequisites or when not to use it.

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/richmcpharlin/google-sheets-mcp'

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