Jupyter MCP Server

Overview Schema Source Related Servers Discussions Admin

delete_cell

Delete a cell from a Jupyter notebook by providing its index. For multiple deletions, remove cells in descending order to avoid index shifting.

Instructions

Delete a specific cell. When deleting many cells, MUST delete them in descending order of their index.

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": {
      "notebook_name": "<notebook_name>",
      "cell_index": "<cell_index>"
    },
    "name": "delete_cell"
  }
}

Input Schema

Name	Required	Description	Default
`cell_index`	Yes	Cell index(0-based)
`notebook_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It correctly indicates the tool performs deletion (a mutation) and provides a crucial order constraint for bulk deletions. However, it lacks details about error handling (e.g., when cell_index is invalid), reversibility, or index shifting after deletion.

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 extremely concise, consisting of two sentences with no redundant information. It front-loads the primary action and adds a critical usage rule in the second sentence.

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?

Given the absence of annotations, the description covers the main action and a key usage rule. However, it omits details like prerequisites (notebook must exist, cell must exist), return value (output schema exists but not described), and error behavior. For a simple deletion tool, it is adequate but not thorough.

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

Parameters2/5

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

Schema coverage is 50% (only cell_index has a description). The description adds no additional meaning for parameters; it does not clarify notebook_name or further explain cell_index beyond what the schema provides. The mention of 'descending order' relates to usage, not parameter semantics.

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 'Delete a specific cell,' which is a specific verb+resource combination. It also distinguishes itself from sibling tools like list_cell, read_cell, and insert_cell by focusing solely on deletion.

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 an explicit guideline: 'When deleting many cells, MUST delete them in descending order of their index.' This is helpful for correct usage. However, it does not explicitly state when to use this tool versus alternatives (e.g., overwrite_cell), but the purpose itself implies deletion is the primary use case.

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

Deploy Server