lb_delete_node
Permanently removes a node from your knowledge graph. Deletion cascades to link rows (both outgoing and incoming) and PARA tag junctions in a single D1 batch, and issues a best-effort cleanup against Vectorize.
This action cannot be undone. The HTTP DELETE /nodes/:id route wraps the same service method.
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | The ID of the node to delete |
Response
Section titled “Response”{ "deleted": true, "id": "..." }Errors
Section titled “Errors”| Code | When |
|---|---|
NOT_FOUND | The node does not exist in the current tenant (or never did) |
Usage notes
Section titled “Usage notes”- Deletion is atomic at the D1 layer: node row,
node_para_tagsjunctions, andlinksrows are deleted in one transaction. Vectorize cleanup runs outside the transaction and is best-effort — a transient Vectorize failure will not roll back the D1 delete. - Prefer archiving via PARA item workflows when the user might want to restore context later. There is no restore path for deleted nodes today.
- Idempotency: calling this tool twice for the same ID returns
NOT_FOUNDon the second call.