Create a new notebook in the database, optionally nested under a parent notebook using its ID from list-notebooks.
Create a new notebook in the database. To create a nested notebook, pass the parent notebook ID as parentBookId. Call list-notebooks first to find it.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The notebook name | |
| parentBookId | No | The ID of the parent notebook. Omit it to create the notebook at the root level. |
Changes observed during successful MCP inspections.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The side effect is made explicit: the tool 'Create[s] a new notebook in the database', indicating a persistent write operation. It does not mention idempotency, permissions, or validation errors, but for a straightforward create operation the primary behavior is disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences with no redundant wording. The primary purpose is stated first, followed by the nested-notebook usage note and prerequisite lookup.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description provides enough context for a simple create operation: what it creates, how to create a nested notebook, and where to find the parent ID. It does not specify the return value or error behavior, but those are not essential for this tool given its clear parameters and schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both parameters are fully described in the schema: name is the notebook name, and parentBookId is the parent notebook ID with a note to omit it for root-level creation. The description adds practical context by telling the user to call list-notebooks first to obtain the parentBookId.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the action ('Create'), the resource ('a new notebook'), and the context ('in the database'). It also distinguishes notebook creation from sibling tools like create-tag, create-note, or create-file by naming the resource type explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides concrete usage guidance by explaining how to create a nested notebook ('pass the parent notebook ID as parentBookId') and instructs the user to 'Call list-notebooks first to find it'. It does not explicitly contrast with sibling create tools, but the resource-specific guidance is clear enough for correct usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.