xlsx-tools-mcp

Overview Schema Source Related Servers Discussions Admin

delete_rows

Remove rows from an Excel .xlsx sheet by 1-based start index, shifting lower rows upward. Skip LibreOffice recalculation for complex workbooks if needed.

Instructions

Delete rows, shifting the rows below them upward.

Set recalculate=False to skip the LibreOffice recompute (e.g. for structurally complex workbooks you don't want round-tripped).

Args: path: Path to the .xlsx file, or the name of a preloaded file. Omit if only one file is configured. sheet: Sheet name. start_row: 1-based row index to start deleting from. count: Number of rows to delete. recalculate: Run the LibreOffice recompute pass after saving.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	No
`count`	No
`sheet`	Yes
`backup`	No
`start_row`	Yes
`recalculate`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Oct 4, 2026

addedInput schema / properties / backup

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Backup"
+}

First observedv0.1.0Aug 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the row-shift semantics and the recompute-skip trade-off, but says nothing about irreversibility, the role of the undocumented backup parameter, or how merges/formulas are affected by a destructive operation.

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?

Purpose and structural consequence are front-loaded, followed by the recalculate nuance and a clean Args list. Slightly verbose as a param list, but each line is informative and no sentence is wasted.

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?

Output schema exists so return values needn't be described, and the core delete semantics are covered. But for a destructive 6-parameter tool with zero annotation coverage, the absence of the backup parameter's meaning and any warning about irreversibility leaves the definition short of complete.

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

Parameters4/5

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

With 0% schema description coverage the description must compensate, and it does for 5 of 6 parameters, clarifying 1-based indexing, the count default semantics, and the preloaded-file behavior of path. It omits the 'backup' parameter entirely, which is the main gap.

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?

States a specific verb+resource ('Delete rows') and immediately describes the structural consequence ('shifting the rows below them upward'), which cleanly separates it from siblings like delete_columns, delete_sheet, and clear_range. An agent can identify the operation without opening the schema.

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?

Gives conditional guidance for one parameter ('Set recalculate=False ... for structurally complex workbooks you don't want round-tripped'), which implicitly tells the agent when to use the non-default path. However, it offers no when-to-use-vs-alternatives routing (e.g. vs clear_range or delete_columns) and no exclusions.

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