notebooklm-mcp

Overview Schema Source Related Servers Discussions Admin

Studio Create

studio_create

Generate any NotebookLM studio artifact—audio, video, infographic, slides, report, flashcards, quiz, data table, or mind map—from your notebook sources.

Instructions

Create any NotebookLM studio artifact. Unified creation tool.

Supports: audio, video, infographic, slide_deck, report, flashcards, quiz, data_table, mind_map

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	No		Mind Map
`confirm`	No	Must be True after user approval
`language`	No
`difficulty`	No		medium
`source_ids`	No	Source IDs to use (default: all sources)
`description`	No
`notebook_id`	Yes	Notebook UUID
`orientation`	No		landscape
`audio_format`	No		deep_dive
`audio_length`	No		default
`detail_level`	No		standard
`focus_prompt`	No
`slide_format`	No		detailed_deck
`slide_length`	No		default
`video_format`	No		explainer
`visual_style`	No		auto_select
`artifact_type`	Yes	Type of artifact to create: - audio: Audio Overview (podcast) - video: Video Overview - infographic: Visual infographic - slide_deck: Presentation slides (PDF) - report: Text report (Briefing Doc, Study Guide, etc.) - flashcards: Study flashcards - quiz: Multiple choice quiz - data_table: Structured data table - mind_map: Visual mind map
`custom_prompt`	No
`report_format`	No		Briefing Doc
`question_count`	No
`report_template`	No		learning_overview
`infographic_style`	No		auto_select
`video_style_prompt`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.12.0Sep 25, 2026
- addedInput schema / properties / report_template
```
Added value: +{
+  "default": "learning_overview",
+  "type": "string"
+}
```

Changed4 schema fields changedv0.11.2Sep 9, 2026

addedInput schema / properties / artifact_type / description

Added value: +"Type of artifact to create:\n- audio: Audio Overview (podcast)\n- video: Video Overview\n- infographic: Visual infographic\n- slide_deck: Presentation slides (PDF)\n- report: Text report (Briefing Doc, Study Guide, etc.)\n- flashcards: Study flashcards\n- quiz: Multiple choice quiz\n- data_table: Structured data table\n- mind_map: Visual mind map"

addedInput schema / properties / confirm / description
```
Added value: +"Must be True after user approval"
```
addedInput schema / properties / notebook_id / description
```
Added value: +"Notebook UUID"
```

addedInput schema / properties / source_ids / description

Added value: +"Source IDs to use (default: all sources)"

Changed1 schema field changedv0.9.12Aug 19, 2026

changedInput schema / properties / source_ids / anyOf

Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

Addedv0.9.1Jul 22, 2026
Removedv0.8.9Jul 18, 2026

Changed4 schema fields changedv0.7.7Jun 20, 2026

removedInput schema / properties / artifact_type / description

Removed value: -"Type of artifact to create:\n- audio: Audio Overview (podcast)\n- video: Video Overview\n- infographic: Visual infographic\n- slide_deck: Presentation slides (PDF)\n- report: Text report (Briefing Doc, Study Guide, etc.)\n- flashcards: Study flashcards\n- quiz: Multiple choice quiz\n- data_table: Structured data table\n- mind_map: Visual mind map"

removedInput schema / properties / confirm / description
```
Removed value: -"Must be True after user approval"
```
removedInput schema / properties / notebook_id / description
```
Removed value: -"Notebook UUID"
```

removedInput schema / properties / source_ids / description

Removed value: -"Source IDs to use (default: all sources)"

First observedv0.6.13May 31, 2026

TDQS

C2.6/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. The description only says it creates artifacts, but does not disclose that a confirmation is required (as indicated by the 'confirm' parameter in the schema), potential side effects like resource consumption, or whether creation is synchronous or asynchronous. The tool is clearly a mutation, but no behavioral details are revealed.

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

Conciseness3/5

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

The description is concise, but structure is minimal: a one-sentence intro followed by a list of supported types. It does not front-load critical information like the confirmation requirement or parameter dependencies. While not verbose, it lacks an organized breakdown of behaviors, which reduces its usefulness.

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 has 23 parameters, many with specific enums-like defaults, and no annotations, the description is severely insufficient. It omits the confirmation flow, return behavior, and parameter interactions. The output schema exists but is not leveraged in the description to clarify what the agent should expect. For a complex creation tool with many options, this is far from complete.

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

Parameters2/5

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

Schema description coverage is only 17%, so the description must compensate. It does not explain the meanings of the many parameters (audio_format, slide_format, video_format, etc.). Only the artifact_type parameter is described indirectly by listing the types. The description provides no additional semantics for the other 21 parameters, leaving the agent to infer or rely on the sparse schema descriptions.

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 clearly states it creates NotebookLM studio artifacts and lists all supported artifact types. The verb 'Create' with a specific resource is present. However, it does not explicitly distinguish itself from sibling studio_revise, though the creation vs. revision distinction is implicit. The listing of artifact types adds specificity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like studio_revise or other related tools. The description calls it a 'unified creation tool' but does not explain when to choose it over other tools or when not to use it. There is no mention of exclusions, prerequisites, or suitable contexts.

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