Skip to main content
Glama

notebook_create

Create a new empty notebook in NotebookLM. Returns the notebook's URL and ID for subsequent operations like adding sources and asking questions.

Instructions

Create a brand-new empty notebook directly in NotebookLM (no pre-existing URL required, unlike add_notebook which only registers an already-created notebook into the library).

Returns { notebook_url, notebook_id, name_applied, actual_name, message }.

  • notebook_url / notebook_id: always the FINAL UUID-based URL (the tool waits past the /notebook/creating/c transitional URL).

  • name_applied (boolean): whether the name parameter actually took effect. false means the notebook is still "Untitled notebook" — rename via UI if needed.

  • actual_name (string): the title observed on the notebook after creation.

Typical workflow:

  1. create_notebook({ name?: "my-research" }){ notebook_url, notebook_id, name_applied, actual_name }

  2. add_source({ notebook_url, source_type: "url", source: "https://..." })

  3. ask_question({ notebook_url, question: "..." })

Note: Requires authentication. Run setup_auth first if not authenticated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional initial title for the notebook. NotebookLM will auto-name it if omitted (usually "Untitled notebook"). The title can be edited later via the UI.
show_browserNoShow browser window during creation. Default: false (headless).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the tool call succeeded.
dataNoThe tool payload on success. The exact shape depends on the tool.
errorNoHuman-readable error message, present only when success is false.
Behavior4/5

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

Annotations already indicate mutation (readOnlyHint=false) and side effects (openWorldHint=true). Description adds valuable context: details about waiting for final URL, the name_applied boolean behavior, and the authentication requirement. This goes beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with purpose first, then detailed return values, then workflow. It is slightly lengthy but every part earns its place. Could be more concise but still clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the moderate complexity (2 parameters, no nesting, output schema exists), the description is fully complete. It explains output fields, provides a usage workflow, and notes authentication prerequisites. No gaps identified.

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 description coverage is 100%, so baseline 3 is appropriate. Description reiterates some parameter info but does not add significant new meaning beyond what the schema already provides for name and show_browser.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states 'Create a brand-new empty notebook directly in NotebookLM' with specific verb and resource. It clearly distinguishes from the sibling add_notebook by noting this tool creates vs registers an existing notebook.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use this tool ('no pre-existing URL required') vs the alternative add_notebook. Also includes a typical workflow of sequential steps to follow after creation, guiding the agent on correct invocation order.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/roomi-fields/notebooklm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server