NotebookLM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notebooksA | List all NotebookLM notebooks owned by the user. |
| create_notebook | Create a new notebook with the given title. |
| add_url_source | Add a web page URL as a source to a notebook. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools; the purpose is clear.
The single tool name 'list_notebooks' follows a clear verb_noun pattern, and consistency is not a concern with one tool.
A single tool for a NotebookLM server feels too thin; most users would expect additional operations beyond listing.
The server only offers listing, lacking essential operations like create, delete, or update, leaving the surface severely incomplete.