Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NOTEBOOKLM_HEADLESSNoSet to true to run browser headless (requires existing session)false
NOTEBOOKLM_USER_DATA_DIRNoPath to Chrome profile for persistent sessions~/.notebooklm-mcp/session

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_notebooksA

List all notebooks available in the user's Google NotebookLM account. Returns notebook titles and IDs.

create_notebookA

Create a new, empty notebook in Google NotebookLM with the given title. The newly created notebook becomes the currently active notebook.

open_notebookA

Open an existing notebook by its title or ID. The opened notebook becomes the currently active notebook for subsequent tool calls.

add_sourceB

Add a source to the currently open notebook. Sources can be a public web URL or arbitrary text content.

query_notebookA

Ask a question to the currently open notebook and receive the AI-generated answer that is grounded in the notebook's sources.

get_notebook_infoA

Retrieve metadata about the currently open notebook: its title, the number of sources, and the list of source titles/URLs.

delete_notebookA

Permanently delete a notebook by its title or ID. This action cannot be undone.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct action: creating, deleting, opening, listing notebooks; adding sources; querying; getting info. No overlap in functionality, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_notebook, add_source, query_notebook), making the interface predictable.

Tool Count5/5

With 7 tools, the set covers the core operations for NotebookLM management without being overly large or too sparse, perfectly scoped for the domain.

Completeness4/5

The tools cover CRUD-like operations for notebooks and basic source management and querying. Minor gaps like the inability to remove a source or rename a notebook exist but do not severely hinder the main workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues