notebooklm-tool-consolidation-v1-to-v2-mapping
Upgrading from the custom 42-tool notebooklm-mcp to upstream 38-tool notebooklm-mcp-cli requires a skill rewrite because tool names consolidate: separate source_add_url/text/file/drive become source_add(source_type=url|text|drive|file), and individual generate_* tools become studio_create(artifact_type=...). Any skill or agent prompt referencing old tool names will fail silently after the upgrade.
Related
- notebooklm-mcp-cli-consolidated-tool-pattern
- notebooklm-mcp-cli-consolidated-tool-architecture
- notebooklm-upstream-consolidates-42-tools-to-38-action-based
- notebooklm-upstream-consolidated-tool-design
- docker
- notebooklm-tool-consolidation-42-to-38-granular-to-action-pa
- standup-reports-table-date-pk-no-id-column
- enterprise-skill-duplicate-sections-post-infra-change