notebooklm-mcp-rpc

Start a research job

research_start

Initiate research on a notebook using web or Drive sources. Fast mode delivers sources in seconds; deep mode provides thorough analysis in 15-30 minutes.

Instructions

Kick off web/Drive research. mode=fast returns ~5-10 sources in seconds; mode=deep runs 15-30 minutes (web only).

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": {
      "notebook": "<notebook>",
      "query": "<query>"
    },
    "name": "research_start"
  }
}

Input Schema

Name	Required	Description
`from`	No
`mode`	No
`query`	Yes
`notebook`	Yes	Notebook UUID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations indicate this is not read-only and is open-world. The description adds context about execution time differences but does not disclose the asynchronous nature, need for polling, or potential side effects. With annotations providing minimal safety info, more transparency is expected.

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?

Two efficient sentences: first states purpose, second details modes. No fluff, front-loaded.

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?

The description covers key dimensions (source, mode) for a job-starting tool. It omits return behavior or polling instructions, but sibling tools fill that gap. Adequate for its role.

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

Parameters4/5

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

With only 25% schema coverage, the description meaningfully explains the 'mode' parameter (fast vs deep times) and implies 'from' options. However, 'query' and 'notebook' are not elaborated beyond schema.

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 tool starts a research job on web or Drive, distinguishing it from sibling tools like research_poll and research_wait. The specific verb 'kick off' and resource listing are precise.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use each mode (fast vs deep) with time estimates, but does not advise against using this tool versus alternatives or mention prerequisites.

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

Deploy Server