Lista os artifacts do notebook. type filtra (audio|video|slide-deck|quiz|flashcard|infographic|data-table|mind-map|report).
Bulk support: accepts notebook_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | ||
| notebook_id | Yes | ||
| notebook_ids | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate the tool is read-only and idempotent. The description adds context about batch processing but does not disclose additional behavioral traits beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences. First sentence front-loads the primary function and filter; second adds batch capability. No redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers core functionality but lacks explanation of return format or what constitutes an artifact, which would be helpful given no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description compensates by listing the allowed type values and explaining batch behavior with notebook_ids. However, the required notebook_id parameter lacks description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists artifacts, specifies the type filter with allowed values, and mentions bulk support. It distinguishes from siblings like get (single) and delete.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context for using the type filter and batch execution but does not explicitly state when to use this tool versus alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes (notebook vs source vs note vs artifact vs sharing). Minor overlap exists between notebooklm_ask and notebooklm_history (both Q&A-related) and between artifact generate/poll/retry, but descriptions help differentiate. Meta-tools like marketplace and authenticate are separate in function.
Core tools follow a consistent notebooklm_{resource}_{action} pattern. However, meta-tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) lack the notebooklm_ prefix, breaking overall naming consistency. Within the core domain, naming is predictable.
43 tools is high but covers a broad domain: notebooks, sources, notes, artifacts (multiple types), sharing, Q&A, plus meta-tools. Some tools could be merged (e.g., share_add/remove/update/view_level), and meta-tools inflate count. Feels slightly heavy but not excessive for the feature set.
Covers full lifecycle for notebooks, sources, notes, artifacts (CRUD plus generate, download, poll, retry, suggestions). Sharing and Q&A have comprehensive operations. Minor gap: no tool to update notebook metadata beyond rename, but overall very complete.