notebooklm-mcp

library_get

Read-onlyIdempotent

Need to inspect a specific notebook? Get its full details, including content and metadata, using just the notebook ID.

Instructions

Get detailed information about a specific notebook by ID

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The notebook ID

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.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds 'detailed information' but no further behavioral traits (e.g., error handling, format). No contradiction.

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?

Single sentence with no unnecessary words; front-loaded with purpose.

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?

Given the tool's simplicity (one parameter, output schema exists), the description is fully adequate.

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% for the single parameter 'id', and the description does not add meaning beyond 'The notebook ID' already in schema. Baseline 3.

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 the action ('get detailed information') and the resource ('a specific notebook by ID'), distinguishing it from sibling tools like library_list (list all) and library_search (search).

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 when to use (when you need details of a known notebook by ID) but provides no exclusions or alternatives among siblings.

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