Skip to main content
Glama
Sign In
notebook-edit

notebook-edit

by tmlksu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_cell

Remove a cell from a notebook using its index or cell ID. Optionally specify an expected revision to prevent conflicts from concurrent edits.

Instructions

Delete a cell, addressed by index (0-based) OR cell_id (exactly one).

Prefer cell_id from list_cells — an id can't drift onto the wrong cell the way a stale index can. Optionally pass expected_rev to guard against concurrent external edits. Returns the new rev.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
indexNo
cell_idNo
expected_revNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / cell_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Cell Id"
+}
    • addedInput schema / properties / expected_rev
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Expected Rev"
+}
    • addedInput schema / properties / index / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / index / default
      Added value: +null
    • removedInput schema / properties / index / type
      Removed value: -"integer"
    • changedInput schema / required
      Previous value: -[
-  "path",
-  "index"
-]New value: +[
+  "path"
+]
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It reveals that deletion returns a new rev and mentions concurrency guard, but it omits important behavioral traits such as irreversibility, permission requirements, or error behavior if both index and cell_id are provided or if the cell doesn't exist.

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 concise (three sentences) and well-structured, front-loading the action and key options without extraneous words.

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 no output schema or annotations, the description is somewhat incomplete. It lacks details on the irreversible nature of deletion, potential failure modes, and the meaning of the returned rev. The missing path parameter explanation further reduces completeness.

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 coverage is 0%, so the description must explain parameters. It effectively describes index, cell_id, and expected_rev, but neglects the required 'path' parameter entirely, which is a significant gap.

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 tool deletes a cell and provides addressing options (index or cell_id). The verb and resource are specific, but it does not explicitly differentiate from sibling tools like edit_cell or move_cell, though the purpose is unambiguous.

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 advises preferring cell_id over index due to drift risk, and suggests using expected_rev for concurrency protection. However, it does not specify when not to use this tool or contrast it with alternatives like patch_cell or delete operations for other resources.

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

Deploy Server

Other Tools