Skip to main content
Glama

download_all_artifacts

Download completed artifacts from one or all NotebookLM notebooks into organized subfolders named after each notebook.

Instructions

Download all completed studio artifacts of one notebook — or every notebook.

Creates a subdirectory of output_dir named after each notebook title and saves every completed artifact there, named after its title with the type's default extension (report → .md, mind_map → .json, video → .mp4, slide_deck → .pdf/.pptx, ...). Artifacts that are still generating or failed are skipped and listed in the result. A failure on one artifact (or one notebook in a sweep) does not stop the others.

Args: notebook_id: Notebook UUID (omit when all_notebooks=True) output_dir: Base directory for the per-notebook folders (default: cwd) artifact_types: Restrict to these types, e.g. ["video", "slide_deck", "mind_map", "report"]. Default: all types. output_format: For quiz/flashcards only: json|markdown|html slide_deck_format: For slide decks only: pdf (default) or pptx all_notebooks: Sweep every notebook in the account instead of one skip_existing: Skip artifacts whose target file already exists — makes repeated runs incremental

Returns: dict with status, output_dir, and per-artifact items (single notebook) or per-notebook outcomes (sweep), plus downloaded/failed counts

Example: download_all_artifacts(notebook_id="abc123", output_dir="exports") download_all_artifacts(all_notebooks=True, output_dir="exports", skip_existing=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_dirNo.
notebook_idNo
all_notebooksNo
output_formatNojson
skip_existingNo
artifact_typesNo
slide_deck_formatNopdf

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, but the description fully discloses behaviors: subdirectory creation, naming conventions, default extensions, skipping unfinished/failed artifacts, and non-blocking failure per artifact. Also explains return structure.

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 long but well-organized with bullet points and examples. Every sentence adds value, though minor redundancy could be trimmed.

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

Completeness5/5

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

For a tool with 7 parameters, no annotations, and an output schema, the description covers all necessary aspects: argument details, behavior, return format, and examples. Sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description explains all 7 parameters with defaults, types, and examples (e.g., notebook_id, artifact_types, output_format). Fully compensates for missing schema 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?

The description clearly states it downloads all completed studio artifacts from one or all notebooks, distinguishing it from sibling tools like download_artifact (single artifact) and 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 Guidelines4/5

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

It explains when to use (download all artifacts from specific notebook or all notebooks) and mentions skipped artifacts. Implicitly distinguishes from single artifact download, but lacks explicit 'when not to use' or alternatives.

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/jacob-bd/gemini-notebook-mcp-cli'

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