Notebooklm-Unofficial-API-MCP

Overview Schema Source Related Servers Discussions Admin

studio_list

Read-only

Retrieve a notebook's Studio panel items—text notes and generated artifacts—with kind filtering, pagination, and detail levels.

Instructions

List a notebook's Studio panel — text notes AND generated artifacts.

Accepts a notebook name or ID. Returns a merged items list; each item has id / title / type (note or a hyphenated artifact kind); artifacts also carry status_label / url. Bounded page of limit (default 50) from offset, with total / offset / has_more.

detail ladder (NOTE bodies only; read a report/data-table body via studio_download): summary (default) gives each note a bounded content_preview + char_count. Artifacts add created_at, generation_prompt, duration_seconds, slide_count, source_count (unknown metadata/counts are null). full = whole content; compact = a id/title/type/status_label/created_at roster.
kind filters to one type.
item (name or id) fetches just that item as a 1-element list with the note's FULL content or the artifact's summary metadata; no match is NOT_FOUND. limit / offset / detail are ignored with item; kind scopes resolution.

Input Schema

TableJSON Schema

Name	Required	Default
`item`	No
`kind`	No
`limit`	No
`detail`	No	summary
`offset`	No
`notebook`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint/destructiveHint), while the description adds substantial behavioral context: the merged items shape, the detail ladder semantics, that item mode ignores limit/offset/detail, that no match is NOT_FOUND rather than empty, and that unknown metadata/counts return null.

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?

Front-loads purpose, then organizes the ladders and modes into bullets. Dense but every sentence carries operational detail; minor redundancy in the overlapping descriptions of detail and item behavior keeps it from a 5.

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 6-parameter listing tool with an output schema, the description still covers the important edge cases an agent needs (item-resolution semantics, ignored params, NOT_FOUND behavior, null metadata) and routes body reading elsewhere. Nothing essential is missing.

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%, so the description carries the full burden and does so: it documents detail levels (summary/full/compact with their exact output), kind as a single-type filter, limit/offset pagination, and item accepting a name or id. Every parameter gains meaning beyond the bare schema.

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?

States a specific verb and resource ('List a notebook's Studio panel') and clarifies scope precisely: both text notes and generated artifacts. This distinguishes it from siblings like studio_status, studio_download, and note_save without needing to open any schema.

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?

Routes the agent explicitly: read a report/data-table body via studio_download, and describes when to use the 'item' fetch mode versus the merged list. It has clear contextual guidance but does not draw an explicit boundary against studio_status or source_list, so it falls just short of a 5.

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