Skip to main content
Glama
tszaks

Gmail Multi-Inbox MCP Server

by tszaks

sheets_insert_dimension

Insert rows or columns into a Google Sheets spreadsheet at a specified zero-based index, specifying the sheet tab and count. Useful for adding data structures programmatically.

Instructions

Insert rows or columns into a sheet at a specified position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of rows or columns to insert.
accountYesAccount id.
dimensionYesWhether to insert rows or columns.
sheet_titleYesSheet tab name.
start_indexYesZero-based index where rows/columns will be inserted.
spreadsheet_idYesSpreadsheet ID.
Behavior2/5

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

With no annotations, the description should disclose side effects such as shifting existing data or that inserted rows/columns are blank. It only states the basic action without any impact details, requiring the agent to infer consequences.

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?

A single sentence of 13 words conveys the core purpose with no redundant information. It is appropriately sized and front-loaded.

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?

This is a mutation tool with no annotations and no output schema. The description does not mention return values, effects on existing data, or prerequisites, leaving the agent without a complete picture for such a multi-parameter operation.

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 coverage is 100% for all six parameters, so the baseline is 3. The description does not add additional parameter semantics beyond referencing 'rows or columns' and 'specified position', which map to dimension and start_index.

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 identifies the action (insert), the target (rows or columns), and the location (specified position). It distinguishes from sibling tools like sheets_delete_dimension and sheets_append by focusing specifically on inserting dimensions.

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 implies usage for inserting structure at a specific position but does not explicitly state when to prefer this over alternatives like sheets_append or sheets_write. No exclusions or alternative tools 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/tszaks/ghub'

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