notebooklm-mcp-cli

Download Artifact

download_artifact

Download any NotebookLM artifact—audio, video, report, mind map, slides, infographic, data table, quiz, or flashcards—to a specified file path. Consolidates all artifact types into one unified download action.

Instructions

Download any NotebookLM artifact to a file.

Unified download tool replacing 9 separate download tools. Supports all artifact types: audio, video, report, mind_map, slide_deck, infographic, data_table, file, quiz, flashcards.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`wait`	No	Poll while the artifact download is still propagating
`artifact_id`	No	Optional specific artifact ID (uses latest if not provided)
`notebook_id`	Yes	Notebook UUID
`output_path`	Yes	Where to save the file, relative to the download directory (e.g. "podcast.m4a" or "My Notebook/report.md"). Downloads are confined to that directory; a path outside it is refused. It defaults to ~/Downloads/gemini-notebook and the operator can move it with NOTEBOOKLM_DOWNLOAD_DIR. The saved absolute path comes back in the result.
`wait_timeout`	No	Maximum seconds to wait when ``wait`` is enabled
`artifact_type`	Yes	Type of artifact to download: - audio: Audio Overview (MP4/MP3) - video: Video Overview (MP4) - report: Report (Markdown) - mind_map: Mind Map (JSON) - slide_deck: Slide Deck (PDF or PPTX) - infographic: Infographic (PNG) - data_table: Data Table (CSV) - data_table_xlsx: Data Table Excel export (XLSX) - file: Generic Studio file export - quiz: Quiz (json\|markdown\|html) - flashcards: Flashcards (json\|markdown\|html)
`output_format`	No	For quiz/flashcards only: json\|markdown\|html (default: json)	json
`poll_interval`	No	Seconds between readiness checks
`slide_deck_format`	No	For slide_deck only: pdf (default) or pptx	pdf

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.5Sep 18, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses scope and unification, but says nothing about download-directory confinement, propagation waits, permissions, output side effects, or failure behavior; these traits are only discoverable by reading the parameter schema.

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 short and front-loaded with the primary action ('Download any NotebookLM artifact') before supporting scope. There is no filler, though the artifact-type list somewhat duplicates information already present in the input schema.

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?

Given a 9-parameter tool with no annotations, the top-level description is thin: it establishes the unified nature and supported artifact types but leaves sibling-tool selection and behavioral caveats to inference. The rich input schema compensates for most parameter-level gaps, so the definition is usable but not fully 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 all 9 parameters are already documented with defaults and constraints. The top-level description adds no parameter-level meaning beyond re-listing artifact type names, which the schema already covers with more detail; this meets the baseline but does not exceed it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific action ('Download'), the resource ('NotebookLM artifact'), and the outcome ('to a file'), then enumerates the supported artifact types. It also identifies itself as the 'Unified download tool replacing 9 separate download tools,' which helps an agent recognize it as the general-purpose download entry point, though it does not explicitly contrast it with download_all_artifacts or export_artifact.

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 general usage with 'any NotebookLM artifact' and 'Unified download tool replacing 9 separate download tools,' but it never explicitly states when to prefer this tool over sibling tools like download_all_artifacts or export_artifact. There are no exclusions, prerequisites, or batch-vs-single-artifact routing cues.

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