notebooklm-mcp

content_list

Read-onlyIdempotent

List all documents, URLs, and audio overviews in the current notebook to see what materials and generated content are available.

Instructions

List all sources and generated content in the current notebook.

Returns:

Sources: Documents, URLs, and other uploaded materials
Generated content: Audio overviews

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session_id`	No	Session ID to reuse an existing session
`notebook_url`	No	Notebook URL. If not provided, uses the active notebook.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	The tool payload on success. The exact shape depends on the tool.
`error`	No	Human-readable error message, present only when success is false.
`success`	Yes	Whether the tool call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.4Jun 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds context about returned categories (sources, generated content) but no additional behavioral traits like pagination or limits.

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

Conciseness5/5

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

Efficient bullet points, front-loaded with main action, every sentence adds value. No wasted words.

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

Completeness4/5

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

With output schema present, return value details are not needed. Description covers the key categories returned. Adequate for a simple list tool.

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%, both parameters described. Description adds no extra meaning beyond what schema provides, so baseline score applies.

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?

Description clearly states it lists sources and generated content in the current notebook, specifying categories. Verb and resource are explicit and distinct from siblings like content_download or content_generate.

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?

No explicit when-to-use or alternatives among siblings. Implied usage for viewing content, but no guidance on when to prefer over other list tools like library_list or notebook_list.

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