notebook_create
Create a new notebook in Google NotebookLM to organize and manage your research sources and notes.
Instructions
Create a new notebook
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Title for the new notebook |
Create a new notebook in Google NotebookLM to organize and manage your research sources and notes.
Create a new notebook
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Title for the new notebook |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description does not disclose any behavioral traits beyond the obvious create action. Lacks details on side effects, permissions, or return values.
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?
Extremely concise single sentence. Could be slightly improved with additional context without being verbose.
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?
For a simple 1-parameter tool with no output schema or annotations, the description is minimally adequate but lacks any behavioral or result context.
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?
Schema covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond what the schema already provides.
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?
Description clearly states action (Create) and resource (a notebook). Distinguishes from sibling tools like notebook_add_drive that modify existing notebooks.
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?
No guidance on when to use this tool vs alternatives like notebook_add_text or notebook_rename. Missing context for choosing this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/moodRobotics/notebooklm-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server