Skip to main content
Glama
Sign In
NotebookLM MCP Server

NotebookLM MCP Server

by Robiton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

source_delete

Permanently delete one or multiple sources from NotebookLM. Requires explicit confirmation to avoid accidental removal.

Instructions

Delete source(s) permanently. IRREVERSIBLE. Requires confirm=True.

Args: source_id: Source UUID to delete (single) source_ids: List of source UUIDs to delete (bulk, alternative to source_id) confirm: Must be True after user approval

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "source_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idNo
source_idsNo
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

A4.3/5.0
Behavior3/5

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

The description warns about the irreversible nature of the operation, which is critical behavioral information. With no annotations provided, it lacks details on authentication, rate limits, associated data destruction, or return value, but the output schema may address the latter.

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?

The description is concise and front-loaded, with every sentence earning its place. It first states the core action and its irreversible nature, then clearly outlines parameters.

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?

Given the tool's 3 parameters and no annotations, the description covers purpose, dual deletion modes, and safety requirements. It does not explain return values (output schema exists) or error conditions, but is largely complete for a delete operation.

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

Parameters5/5

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

Despite 0% schema description coverage, the description adds meaning by explaining source_id for single deletion, source_ids for bulk alternative, and confirm as a user approval requirement, going beyond schema types and defaults.

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 verb 'Delete' and resource 'source(s)', and emphasizes the permanent and irreversible nature, distinguishing it from sibling tools like source_add, source_rename, and source_describe.

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 notes that confirm=True is required and explains the two deletion modes via source_id and source_ids. However, it does not explicitly specify when to use this tool versus alternatives, though siblings are contextually distinct.

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