Skip to main content
Glama
Sign In
notebooklm

notebooklm

by dfelix-net
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_source_url

Add a website or YouTube URL as a source to a notebook by passing the notebook ID and the link, enabling source-grounded research.

Instructions

Adiciona um site ou vídeo do YouTube (URL) como fonte de um caderno.

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>",
      "url": "<url>"
    },
    "name": "add_source_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
notebook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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, yet it only restates the mutation. It does not disclose what happens on duplicate URLs, whether the notebook must pre-exist, what errors are returned, or whether the source is processed asynchronously.

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 that front-loads the verb and resource. Nothing is wasted, though it is terse enough to omit useful context rather than being over-long.

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 two-parameter mutation with no annotations, no output schema, and 0% parameter description coverage, the description is thin. It omits notebook_id semantics, prerequisite conditions, and result/error behavior, leaving the agent to infer much of how to invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It usefully tells the agent that 'url' accepts a website or YouTube link (a format constraint the schema does not convey), but it says nothing about 'notebook_id' beyond implying it identifies the target notebook.

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 states a specific verb ('Adiciona') and resource ('site ou vídeo do YouTube (URL) como fonte de um caderno'), clearly framing the action as attaching a URL source to a notebook. It implicitly contrasts with the sibling add_source_text by specifying URL-based sources, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the mention of 'site ou vídeo do YouTube (URL)' suggests this is the tool for link-based sources, versus add_source_text for pasted text. There is no explicit when-to-use/when-not statement and no mentioned prerequisites such as the notebook having to exist first.

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