Skip to main content
Glama
Sign In
notebooklm-mcp-rpc

notebooklm-mcp-rpc

by sanjeev7e
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Add a text source

source_add_text

Add raw text content as a source to a NotebookLM notebook by specifying the notebook ID and text content.

Instructions

Paste raw text as a source.

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>",
      "content": "<content>"
    },
    "name": "source_add_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
contentYes
notebookYesNotebook UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Description only says 'Paste raw text as a source,' implying a mutation. Annotations provide readOnlyHint=false and openWorldHint=true, but no additional behavioral details are disclosed (e.g., whether it appends to existing sources, uniqueness constraints, or required permissions).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but lacks sufficient detail. It is front-loaded but under-specified for a utility tool.

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?

For a tool that creates a resource, the description omits return value, error conditions, and side effects. No output schema. The description alone is insufficient for an agent to fully understand the tool's behavior.

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

Parameters2/5

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

Schema description coverage is 33% (only notebook has a description). The description does not explain 'title' or 'content' parameters beyond implying 'raw text'. It adds no semantic guidance beyond the 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 'Paste raw text as a source.' clearly states the tool's action (add) and resource (text source). It distinguishes from the sibling source_add_url, which adds from a URL.

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 versus alternatives like source_add_url or other source methods. Lacks context for appropriate use or preconditions.

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