Skip to main content
Glama

Insert Rows

insert_rows

Insert blank rows into an open Excel workbook at a chosen row index, shifting existing rows down to create space for new data.

Instructions

Insert one or more blank rows, shifting existing rows down.

Args: workbook: Workbook name or path (None = active workbook). sheet: Worksheet name (None = active sheet). row_index: 1-based row number the new rows are inserted before (required). count: How many rows to insert.

Returns: JSON confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
sheetNo
workbookNo
row_indexNo
Behavior3/5

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

The description discloses the key side effect (shifting rows down) and the requirement of row_index, but with no safety annotations, it omits other behavioral aspects such as potential impact on formulas, formatting, or undoability. It provides minimal but useful transparency.

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?

The description is well-structured with a front-loaded summary, a clean Args list, and a Returns line. Every sentence is purposeful, and the format makes it easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the action, all parameters, and the expected return value, making it sufficient for a simple insertion tool. Minor gaps like error handling or behavior when workbook/sheet is missing are acceptable, but a note on preservation of formatting or formulas would have made it more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no parameter descriptions (0% coverage), but the description fully compensates by explaining each parameter: workbook and sheet defaults, row_index as 1-based and required, and count as how many rows. This adds substantial meaning beyond the bare schema.

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 specific action: 'Insert one or more blank rows, shifting existing rows down.' This distinguishes it from sibling tools like delete_rows and insert_columns, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly indicates when to use the tool (to insert rows), but it does not explicitly mention alternatives or when not to use it. The context is sufficient for an agent to infer its use case, but lacks explicit exclusion guidance.

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/trustypangolin/excel-mcp-live'

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