Skip to main content
Glama
Sign In
research-hub

research-hub

by WenyuChiou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notebooklm_bundle

Build a NotebookLM upload bundle for a research cluster, optionally including PDF downloads.

Instructions

Build a NotebookLM upload bundle for a cluster.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_slug": "<cluster_slug>"
    },
    "name": "notebooklm_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_slugYes
download_pdfsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral information. It does not disclose side effects, authorization needs, or what the output represents beyond 'build'. The agent cannot tell if this triggers uploads or modifies state.

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?

The description is a single sentence with no wasted words. However, it is at the edge of being too terse, sacrificing necessary detail for brevity.

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

Completeness2/5

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

Despite a simple parameter set and an output schema, the description lacks essential context: what is a bundle, when to build vs. upload, and how the output is used. It is incomplete for a tool with many siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not reference the two parameters (cluster_slug and download_pdfs) at all. With 0% schema description coverage, the description should compensate but fails to explain how each parameter affects the bundle.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Build) and the resource (NotebookLM upload bundle) with context (for a cluster). It distinguishes itself from sibling tools like notebooklm_upload and notebooklm_download, but could be more specific about the bundle contents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs. alternatives such as notebooklm_upload or notebooklm_generate. The description lacks any contextual hints about prerequisites or conditions.

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

Deploy Server

Other Tools