Skip to main content
Glama
Sign In
notebooklm

notebooklm

by dfelix-net
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_source_text

Adds a text source to a notebook so its content can ground questions and generated outputs like podcasts, reports, or slides.

Instructions

Adiciona um texto como fonte de um caderno (ex.: conteúdo de uma peça ou decisão).

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_id": "<notebook_id>",
      "title": "<title>",
      "text": "<text>"
    },
    "name": "add_source_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
titleYes
notebook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a write that attaches a source, but says nothing about whether the notebook must already exist, what happens on duplicate titles, whether removal is possible, or what the call returns.

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?

A single compact sentence with the purpose front-loaded and an example in parentheses. Nothing is wasted, though the brevity contributes to the missing usage and behavioral detail.

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 required-3-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It gives a one-line purpose but does not compensate for the absent parameter and behavior documentation.

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 coverage is 0% and the description only hints that the text payload is the source content (via the parenthetical example). It adds no meaning for 'title' or 'notebook_id' beyond their self-evident names, leaving half the parameter semantics undocumented.

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?

States a specific verb ('Adiciona') and resource ('um texto como fonte de um caderno'), and the parenthetical example clarifies the kind of text. It implicitly separates itself from the sibling add_source_url by specifying text rather than a URL, though it never names that sibling.

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 when-to-use guidance is given, and the obvious alternative, add_source_url (also adding a source to a notebook), is never mentioned. An agent must infer from the word 'texto' alone that this is for inline text content rather than a link.

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