xlide-excel-word-powerpoint-access-office-vba-mcp

Overview Schema Source Related Servers Discussions Admin

Insert, delete or size rows and columns

xlide_manage_rows_columns

DestructiveIdempotent

Insert, delete, resize, hide, show, group, or ungroup rows and columns in Excel files while preserving formula references. Works on .xlsx, .xlsm, and .xlam.

Instructions

Inserts, deletes, resizes, hides, shows, groups or ungroups whole rows or columns. Inserting and deleting move every reference in the workbook with them: a formula pointing below an inserted row follows it, and one pointing into deleted cells becomes #REF!, exactly as Excel does it. Deleting has no undo, so ask the user first. Widths are in characters and heights in points, which is what Excel's own dialogs use. Works on .xlsx, .xlsm and .xlam.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	No	For resize: column width in characters, or row height in points. -1 restores the sheet default.
`count`	No	How many, counting from first.
`first`	Yes	First row or column, 1-based. Column A is 1.
`sheet`	Yes	Worksheet name, matched without case.
`which`	Yes	'rows' or 'columns'.
`action`	Yes	insert, delete, resize, hide, show, group or ungroup.
`collapsed`	No	For group: start the new group collapsed.
`file_path`	Yes	Absolute path to the Excel file.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Even though annotations already mark destructiveHint and readOnlyHint, the description adds essential behavior beyond them: formulas follow inserted rows, references into deleted cells become #REF!, deletion has no undo, and units are Excel-native. This is exactly the kind of contextual disclosure an agent needs.

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?

Four sentences, each earning its place: the operation list, formula/reference consequences, undo warning, and unit/file-format context. Information is front-loaded and free of filler.

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

Completeness5/5

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

With an output schema, annotations, full parameter schema, and detailed behavioral notes, nothing essential is missing. The description covers safety (no undo), units, supported file formats, and Excel-compatible semantics, making it fully actionable.

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 100%, so the schema already documents every parameter. The description's mention of character/point units is valuable but duplicates the schema's parameter descriptions, adding no new parameter-level meaning.

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 opens with a specific verb and resource: 'Inserts, deletes, resizes, hides, shows, groups or ungroups whole rows or columns.' This fully enumerates the tool's scope and clearly differentiates it from sibling tools like manage_sheet or manage_table, which operate on different resources.

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 usage context is explicit: any row/column structure manipulation belongs herecing, not implied. However, it doesn't name alternatives or state when not to use this tool, so it stops short of the highest bar.

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

Deploy Server