jupyter-editor-mcp

Overview Schema Source Related Servers Discussions Admin

ipynb_delete_cell

Delete a cell at a specified index from a Jupyter Notebook (.ipynb) file. Provide the notebook path and cell index to remove the cell and receive the updated cell count.

Instructions

Delete cell at specified index in a Jupyter Notebook (.ipynb).

Args: ipynb_filepath: Path to Jupyter Notebook (.ipynb) file (absolute path preferred) cell_index: Index of cell to delete (0-based indexing)

Returns: Dict with 'success' and 'new_cell_count' or 'error' key

Note: Indices of cells after the deleted cell will shift by -1

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ipynb_filepath": "<ipynb_filepath>",
      "cell_index": "<cell_index>"
    },
    "name": "ipynb_delete_cell"
  }
}

Input Schema

Name	Required	Description	Default
`cell_index`	Yes
`ipynb_filepath`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description discloses some behavioral details such as the shift of indices after deletion and the return dictionary. However, it does not mention whether the file is overwritten in place or any potential destructive side effects beyond the deletion itself.

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 Args, Returns, and Note sections. It is efficient and each piece of information adds value, though it could be slightly more compact while retaining the same information.

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 the tool's simplicity, the description covers inputs, outputs, and a key side effect (index shift). It mentions the error key for failures, making it reasonably complete for the operation described.

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 input schema has no descriptions for parameters, but the description fully compensates by explaining 'ipynb_filepath' (with absolute path preference) and 'cell_index' (0-based indexing). This provides critical meaning that the schema lacks.

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 action ('Delete cell at specified index') and the resource ('Jupyter Notebook (.ipynb)'). This distinguishes it from sibling tools like ipynb_delete_cells_batch by explicitly focusing on a single cell deletion at a given index.

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 deleting a single cell by index but does not explicitly mention alternatives or when not to use it. There is no reference to batch deletion or other related tools, so the guidance is moderate.

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