Skip to main content
Glama

source_add

Add a URL, text, Google Drive document, or local file to a NotebookLM notebook. Supports multiple source types through a single tool.

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. Supported extensions: PDF, TXT, MD, DOCX, CSV, EPUB, MP3, M4A, WAV, AAC, OGG, OPUS, MP4, JPG, JPEG, PNG, GIF, WEBP. Image-bearing sources (PDF / JPG / PNG / etc.) feed Studio video generation's visual-crop pipeline — charts, photos, and diagrams may be extracted as on-screen aids in Video Overviews.
wait_timeoutNoMax seconds to wait if wait=True (default 120)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It does not mention that the tool can be synchronous (with wait parameter) or any side effects, idempotency, or auth requirements. It only states the basic action.

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

Conciseness4/5

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

The description is extremely concise with two short sentences, no fluff, but it could be slightly more informative without sacrificing conciseness.

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

Completeness2/5

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

Given the tool complexity (11 parameters, conditional dependencies, async behavior), the description is too sparse. It does not guide the agent on how to choose parameters for different source types or explain the wait mechanism.

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 coverage is 100%, so the description adds minimal value beyond the schema. It lists supported types but does not explain conditional parameter usage or provide patterns for each source type.

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?

The description clearly states the action ('Add a source to a notebook') and the resource ('notebook'), and specifies it is a unified tool for all source types (url, text, drive, file), distinguishing it from sibling tools like source_delete or source_describe.

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

Usage Guidelines4/5

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

The description implies it is the primary tool for adding sources with 'Unified tool for all source types', but does not provide explicit when-to-use or when-not-to-use guidance or mention alternatives for other operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlexanderKast/cast-notebooklm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server