notebooklm-api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | Your Gemini API key from aistudio.google.com |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_storeA | Create a new document store for uploading and searching files. |
| list_storesA | List all document stores. |
| upload_documentA | Upload a document to a store. Supports PDF, DOCX, TXT, HTML, CSV, and more. Waits for processing to complete before returning. |
| list_documentsB | List all documents in a store. |
| askA | Ask a question about your documents. Returns an answer with per-passage citations mapping every claim to its source document and exact passage. This is the core tool — use it after uploading documents to a store. |
| delete_documentA | Delete a document from a store. |
| delete_storeA | Delete a store and optionally all its documents. |
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 7 tools
Each tool targets a distinct resource action: store creation/listing/deletion, document upload/listing/deletion, and question answering. The 'ask' tool is clearly separated from file management operations, so an agent should not confuse any two tools.
Most tools follow a clear verb_noun snake_case pattern (create_store, list_documents, delete_document). The plural forms in list_stores/list_documents and the bare-verb 'ask' are minor deviations, but they do not undermine readability.
Seven tools is a well-scoped size for this document Q&A server. Each tool covers a necessary part of the workflow without redundancy or bloat.
The store and document lifecycles are mostly covered: create, list, delete, and upload, plus the core ask/search capability. The only noticeable gaps are update/replace operations and a simple get-document detail operation, but these are not critical for the intended workflow.