nblm-mcp
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check whether this server has a working NotebookLM session. Call this first when any other tool reports an auth problem. It performs a real (cheap) request, so it distinguishes "no cookies stored" from "cookies stored but expired". |
| list_notebooksA | List the notebooks reachable by the signed-in Google account. Returns id, title, and source count for each. Use the ids with every other tool — NotebookLM has no lookup by title. |
| get_notebookC | Get one notebook with its sources. |
| create_notebookA | Create an empty notebook. A notebook with no sources cannot answer questions — follow up with add_source before calling ask. |
| delete_notebookA | Permanently delete a notebook and everything in it. This cannot be undone and deletes the notebook's sources, chats, and generated artifacts along with it. |
| list_sourcesB | List the sources in a notebook, with their processing status. A source that is not |
| add_sourceA | Add one source to a notebook, from a URL, pasted text, or a local file. Pass exactly one of |
| delete_sourceC | Remove a source from a notebook. |
| askA | Ask a notebook a question and get an answer grounded in its sources. The answer comes from Gemini reading the notebook's own sources, with citations back to them — use this instead of summarizing the sources yourself when a notebook already holds the material. |
| chat_historyB | Read past question/answer turns for a notebook's current conversation. |
| list_artifactsA | List generated Studio artifacts in a notebook. Use this to poll a generation started with wait=false: the artifact reports
|
| generate_artifactA | Generate a Studio artifact (podcast, report, quiz, mind map...). Generation runs server-side and is slow — an audio overview commonly takes several minutes — and it consumes the account's daily Studio quota. Prefer the default wait=false and poll with list_artifacts. |
| download_artifactB | Download a completed Studio artifact to a file on the server host. |
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 13 tools
Most tools target a distinct resource+action (notebook CRUD, source add/delete/list, artifact generate/list/download, ask, auth). Minor overlap between get_notebook (returns notebook with sources) and list_sources (sources with processing status), but descriptions clarify the difference.
Strong verb_noun pattern for most tools (add_source, list_notebooks, create_notebook, list_artifacts, generate_artifact, download_artifact). A few deviations—ask (bare verb), chat_history and auth_status (noun phrases)—but overall readable and predictable.
13 tools is well-scoped for the NotebookLM domain, cleanly grouped into notebooks, sources, artifacts, and query/auth concerns. Each tool earns its place with no filler.
Good CRUD/lifecycle coverage: notebook create/get/list/delete, source add/delete/list, artifact generate/list/download, plus ask, chat_history, and auth_status. Minor gaps like notebook rename/update and source update, but core workflows are covered.