update_notebook
Modify notebook metadata including topics, description, tags, and use cases to keep content organized and current.
Instructions
Update notebook metadata based on user intent.
Pattern
Identify target notebook and fields (topics, description, use_cases, tags, url)
Propose the exact change back to the user
After explicit confirmation, call this tool
Examples
User: "React notebook also covers Next.js 14" You: "Add 'Next.js 14' to topics for React?" User: "Yes" → call update_notebook
User: "Include error handling in n8n description" You: "Update the n8n description to mention error handling?" User: "Yes" → call update_notebook
Tip: You may update multiple fields at once if requested.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The notebook ID to update | |
| name | No | New display name | |
| description | No | New description | |
| topics | No | New topics list | |
| content_types | No | New content types | |
| use_cases | No | New use cases | |
| tags | No | New tags | |
| url | No | New notebook URL |
Input Schema (JSON Schema)
{
"properties": {
"content_types": {
"description": "New content types",
"items": {
"type": "string"
},
"type": "array"
},
"description": {
"description": "New description",
"type": "string"
},
"id": {
"description": "The notebook ID to update",
"type": "string"
},
"name": {
"description": "New display name",
"type": "string"
},
"tags": {
"description": "New tags",
"items": {
"type": "string"
},
"type": "array"
},
"topics": {
"description": "New topics list",
"items": {
"type": "string"
},
"type": "array"
},
"url": {
"description": "New notebook URL",
"type": "string"
},
"use_cases": {
"description": "New use cases",
"items": {
"type": "string"
},
"type": "array"
}
},
"required": [
"id"
],
"type": "object"
}