Skip to main content
Glama
hyunjae-labs

xlwings Excel MCP Server

delete_sheet_rows

Remove specific rows from Excel worksheets to clean data or adjust spreadsheet structure. Specify sheet name, starting row, and number of rows to delete.

Instructions

Delete one or more rows starting at the specified row.

Args:
    sheet_name: Name of worksheet
    start_row: Row number to start deleting from
    session_id: Session ID from open_workbook (preferred)
    filepath: Path to Excel file (legacy, deprecated)
    count: Number of rows to delete
    
Note: Use session_id for better performance. filepath parameter is deprecated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_nameYes
start_rowYes
session_idNo
filepathNo
countNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool registration for 'delete_sheet_rows' with @mcp.tool decorator. Handles both session-based and legacy filepath modes by delegating to implementation functions.
    @mcp.tool()
    def delete_sheet_rows(
        sheet_name: str,
        start_row: int,
        session_id: Optional[str] = None,
        filepath: Optional[str] = None,
        count: int = 1
    ) -> str:
        """
        Delete one or more rows starting at the specified row.
        
        Args:
            sheet_name: Name of worksheet
            start_row: Row number to start deleting from
            session_id: Session ID from open_workbook (preferred)
            filepath: Path to Excel file (legacy, deprecated)
            count: Number of rows to delete
            
        Note: Use session_id for better performance. filepath parameter is deprecated.
        """
        try:
            # Support both new (session_id) and old (filepath) API
            if session_id:
                # New API: use session
                session = SESSION_MANAGER.get_session(session_id)
                if not session:
                    return ERROR_TEMPLATES['SESSION_NOT_FOUND'].format(
                        session_id=session_id, 
                        ttl=10  # Default TTL is 10 minutes (600 seconds)
                    )
                
                with session.lock:
                    from xlwings_mcp.xlwings_impl.rows_cols_xlw import delete_sheet_rows_xlw_with_wb
                    result = delete_sheet_rows_xlw_with_wb(session.workbook, sheet_name, start_row, count)
            elif filepath:
                # Legacy API: backwards compatibility
                logger.warning("Using deprecated filepath parameter. Please use session_id instead.")
                full_path = get_excel_path(filepath)
                from xlwings_mcp.xlwings_impl.rows_cols_xlw import delete_sheet_rows_xlw
                result = delete_sheet_rows_xlw(full_path, sheet_name, start_row, count)
            else:
                return ERROR_TEMPLATES['PARAMETER_MISSING'].format(
                    param1='session_id',
                    param2='filepath'
                )
            
            if "error" in result:
                return f"Error: {result['error']}"
            return result["message"]
            
        except (ValidationError, SheetError) as e:
            return f"Error: {str(e)}"
        except Exception as e:
            logger.error(f"Error deleting rows: {e}")
            raise
  • Core implementation of row deletion logic using xlwings API. Handles file opening, sheet access, row deletion via COM API, saving, and cleanup.
    def delete_sheet_rows_xlw(
        filepath: str,
        sheet_name: str,
        start_row: int,
        count: int = 1
    ) -> Dict[str, Any]:
        """
        Delete one or more rows in Excel using xlwings.
        
        Args:
            filepath: Path to Excel file
            sheet_name: Name of worksheet
            start_row: Row number to start deletion (1-based)
            count: Number of rows to delete
            
        Returns:
            Dict with success message or error
        """
        app = None
        wb = None
    
        # Initialize COM for thread safety (Windows)
        _com_initialize()
    
        try:
            logger.info(f"Deleting {count} rows starting from row {start_row} in {sheet_name}")
            
            # Check if file exists
            if not os.path.exists(filepath):
                return {"error": f"File not found: {filepath}"}
            
            # Open Excel app and workbook
            app = xw.App(visible=False, add_book=False)
            wb = app.books.open(filepath)
            
            # Check if sheet exists
            sheet_names = [s.name for s in wb.sheets]
            if sheet_name not in sheet_names:
                return {"error": f"Sheet '{sheet_name}' not found"}
            
            sheet = wb.sheets[sheet_name]
            
            # Delete rows using xlwings
            # Delete from bottom to top to maintain row indices
            for i in range(count):
                row_to_delete = sheet.range(f"{start_row}:{start_row}")
                row_to_delete.api.Delete()
            
            # Save the workbook
            wb.save()
            
            logger.info(f"✅ Successfully deleted {count} rows starting from row {start_row}")
            return {
                "message": f"Successfully deleted {count} rows starting from row {start_row}",
                "sheet": sheet_name,
                "start_row": start_row,
                "count": count
            }
            
        except Exception as e:
            logger.error(f"Error deleting rows: {e}")
            return {"error": str(e)}
            
        finally:
            if wb:
                wb.close()
            if app:
                app.quit()
  • Helper function for session-based row deletion, using pre-opened workbook object without file I/O.
    def delete_sheet_rows_xlw_with_wb(
        wb,
        sheet_name: str,
        start_row: int,
        count: int = 1
    ) -> Dict[str, Any]:
        """Session-based version using existing workbook object.
        
        Args:
            wb: Workbook object from session
            sheet_name: Name of worksheet
            start_row: Row number to start deletion (1-based)
            count: Number of rows to delete
            
        Returns:
            Dict with success message or error
        """
        try:
            logger.info(f"🗑️ Deleting {count} rows starting from row {start_row} in {sheet_name}")
            
            # Check if sheet exists
            sheet_names = [s.name for s in wb.sheets]
            if sheet_name not in sheet_names:
                return {"error": f"Sheet '{sheet_name}' not found"}
            
            sheet = wb.sheets[sheet_name]
            
            # Delete rows using xlwings
            # Delete from bottom to top to maintain row indices
            for i in range(count):
                row_to_delete = sheet.range(f"{start_row}:{start_row}")
                row_to_delete.api.Delete()
            
            # Save the workbook
            wb.save()
            
            logger.info(f"✅ Successfully deleted {count} rows starting from row {start_row}")
            return {
                "message": f"Successfully deleted {count} rows starting from row {start_row}",
                "sheet": sheet_name,
                "start_row": start_row,
                "count": count
            }
            
        except Exception as e:
            logger.error(f"Error deleting rows: {e}")
            return {"error": str(e)}
Behavior3/5

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

With no annotations provided, the description carries the full burden. It clearly indicates a destructive operation ('Delete'), which is helpful, but doesn't disclose other behavioral traits like whether deletions are permanent/irreversible, if there are confirmation prompts, performance implications, or error handling. The performance note about session_id is a positive addition.

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 well-structured with a clear purpose statement followed by parameter explanations and usage notes. Every sentence adds value, though the 'Args:' section formatting could be slightly more concise. The information is front-loaded with the core functionality stated first.

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?

Given this is a destructive operation with 5 parameters and no annotations, the description does a good job covering the essentials: purpose, parameters, and some behavioral context. The existence of an output schema means return values don't need explanation. However, for a deletion tool, more explicit warnings about data loss and prerequisites would improve completeness.

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 description provides excellent parameter semantics beyond the 0% schema coverage. It explains what each parameter does ('sheet_name: Name of worksheet', 'start_row: Row number to start deleting from'), gives usage guidance ('session_id from open_workbook (preferred)', 'filepath... deprecated'), and clarifies defaults ('count: Number of rows to delete' with implied default of 1). This fully compensates for the lack of schema descriptions.

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 ('Delete one or more rows') and the target ('starting at the specified row'), which is specific and actionable. It distinguishes from sibling tools like 'delete_range' and 'delete_sheet_columns' by focusing on rows, but doesn't explicitly differentiate from 'delete_worksheet' which removes entire worksheets.

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 provides clear context on when to use certain parameters ('Use session_id for better performance. filepath parameter is deprecated'), which helps guide parameter selection. However, it lacks explicit guidance on when to use this tool versus alternatives like 'delete_range' or 'delete_worksheet', and doesn't mention prerequisites like needing an open workbook session.

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/hyunjae-labs/xlwings-mcp-server'

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