Skip to main content
Glama
jacob-bd

notebooklm-mcp

by jacob-bd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Source Add

source_add

Add any source type—URL, text, Google Drive, or local file—to a NotebookLM notebook in one call. Streamlines research by consolidating multiple input formats into a single operation.

Instructions

Add a source to a notebook. Unified tool for all source types.

Supports: url, text, drive, file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to add (for source_type=url)
textNoText content to add (for source_type=text)
urlsNoList of URLs to add in bulk (for source_type=url, alternative to url)
waitNoIf True, wait for source processing to complete before returning
titleNoDisplay title (for text sources)
doc_typeNoDrive doc type: doc|slides|sheets|pdf (for source_type=drive)doc
file_pathNoLocal file path on the machine running the MCP server (for source_type=file). A path on a different client/agent host is not accessible to the server.
document_idNoGoogle Drive document ID (for source_type=drive)
notebook_idYesNotebook UUID
source_typeYesType of source to add: - url: Web page or YouTube URL - text: Pasted text content - drive: Google Drive document - file: Local file upload. The canonical local-admission contract has 43 case-insensitive extensions. Admission does not guarantee provider processing success for an individual file. OFFICIAL_FILE_EXTENSIONS: .pdf, .txt, .md, .docx, .csv, .pptx, .epub, .avif, .bmp, .gif, .heic, .heif, .ico, .jp2, .jpe, .jpeg, .jpg, .png, .tif, .tiff, .webp, .3g2, .3gp, .aac, .aif, .aifc, .aiff, .amr, .au, .avi, .cda, .m4a, .mid, .mp3, .mp4, .mpeg, .ogg, .opus, .ra, .ram, .snd, .wav, .wma Image-bearing sources may feed Studio video generation's visual-crop pipeline; charts, photos, and diagrams may be extracted as on-screen aids.
wait_timeoutNoMax seconds to wait if wait=True (default 120)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.11.2
    • addedInput schema / properties / doc_type / description
      Added value: +"Drive doc type: doc|slides|sheets|pdf (for source_type=drive)"
    • addedInput schema / properties / document_id / description
      Added value: +"Google Drive document ID (for source_type=drive)"
    • addedInput schema / properties / file_path / description
      Added value: +"Local file path on the machine running the MCP server\n(for source_type=file). A path on a different client/agent host\nis not accessible to the server."
    • addedInput schema / properties / notebook_id / description
      Added value: +"Notebook UUID"
    • addedInput schema / properties / source_type / description
      Added value: +"Type of source to add:\n- url: Web page or YouTube URL\n- text: Pasted text content\n- drive: Google Drive document\n- file: Local file upload. The canonical local-admission contract has\n    43 case-insensitive extensions. Admission does not guarantee provider\n    processing success for an individual file.\n    OFFICIAL_FILE_EXTENSIONS: .pdf, .txt, .md, .docx, .csv, .pptx, .epub, .avif, .bmp, .gif, .heic, .heif, .ico, .jp2, .jpe, .jpeg, .jpg, .png, .tif, .tiff, .webp, .3g2, .3gp, .aac, .aif, .aifc, .aiff, .amr, .au, .avi, .cda, .m4a, .mid, .mp3, .mp4, .mpeg, .ogg, .opus, .ra, .ram, .snd, .wav, .wma\n    Image-bearing sources may feed Studio video generation's visual-crop\n    pipeline; charts, photos, and diagrams may be extracted as on-screen aids."
    • addedInput schema / properties / text / description
      Added value: +"Text content to add (for source_type=text)"
    • addedInput schema / properties / title / description
      Added value: +"Display title (for text sources)"
    • addedInput schema / properties / url / description
      Added value: +"URL to add (for source_type=url)"
    • addedInput schema / properties / urls / description
      Added value: +"List of URLs to add in bulk (for source_type=url, alternative to url)"
    • addedInput schema / properties / wait / description
      Added value: +"If True, wait for source processing to complete before returning"
    • addedInput schema / properties / wait_timeout / description
      Added value: +"Max seconds to wait if wait=True (default 120)"
  2. Changed1 schema field changedv0.9.12
    • changedInput schema / properties / urls / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Addedv0.9.1
  4. Removedv0.9.1
  5. Addedv0.8.9
  6. Removedv0.8.9
  7. Changed11 schema fields changedv0.7.7
    • removedInput schema / properties / doc_type / description
      Removed value: -"Drive doc type: doc|slides|sheets|pdf (for source_type=drive)"
    • removedInput schema / properties / document_id / description
      Removed value: -"Google Drive document ID (for source_type=drive)"
    • removedInput schema / properties / file_path / description
      Removed value: -"Local file path (for source_type=file)"
    • removedInput schema / properties / notebook_id / description
      Removed value: -"Notebook UUID"
    • removedInput schema / properties / source_type / description
      Removed value: -"Type of source to add:\n- url: Web page or YouTube URL\n- text: Pasted text content\n- drive: Google Drive document\n- file: Local file upload. Supported extensions:\n    PDF, TXT, MD, DOCX, CSV, EPUB, MP3, M4A, WAV, AAC, OGG,\n    OPUS, MP4, JPG, JPEG, PNG, GIF, WEBP. Image-bearing\n    sources (PDF / JPG / PNG / etc.) feed Studio video\n    generation's visual-crop pipeline — charts, photos, and\n    diagrams may be extracted as on-screen aids in Video\n    Overviews."
    • removedInput schema / properties / text / description
      Removed value: -"Text content to add (for source_type=text)"
    • removedInput schema / properties / title / description
      Removed value: -"Display title (for text sources)"
    • removedInput schema / properties / url / description
      Removed value: -"URL to add (for source_type=url)"
    • removedInput schema / properties / urls / description
      Removed value: -"List of URLs to add in bulk (for source_type=url, alternative to url)"
    • removedInput schema / properties / wait / description
      Removed value: -"If True, wait for source processing to complete before returning"
    • removedInput schema / properties / wait_timeout / description
      Removed value: -"Max seconds to wait if wait=True (default 120)"
  8. First observedv0.6.13

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must disclose safety and side-effect behavior, but it only restates the action and supported source types. It does not mention that adding a source creates a notebook resource, may be asynchronous unless wait=True, or has file-system/admission caveats; those live in the schema rather than the description.

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

Conciseness5/5

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

Three short sentences, no filler, and the operative verb and scope are front-loaded. Every sentence contributes by naming the resource, the unified nature, and the supported source types.

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

Completeness3/5

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

The schema is rich enough to guide per-parameter invocation, and an output schema exists, so the description does not need to discuss return values. However, for a tool with 11 parameters and no annotations, the description leaves general behavioral context and sibling-tool routing unstated; it is minimally adequate but not complete.

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 the input schema already documents all 11 parameters. The description's 'Supports: url, text, drive, file' matches source_type choices but adds no parameter-level meaning beyond the schema's existing per-parameter descriptions.

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 names a specific action and resource ('Add a source to a notebook') and immediately lists supported source types, making it clear this is the ingestion tool rather than sibling operations like source_describe or source_delete. 'Unified tool for all source types' further establishes its scope.

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

Usage Guidelines3/5

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

The description implies when to use it (adding any of url, text, drive, file to a notebook) but does not explicitly contrast it with siblings such as source_list_drive, source_sync_drive, or source_get_content. There is no 'when not to use' guidance beyond the implied add-vs-manage distinction.

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

Deploy Server

Other Tools