Skip to main content
Glama
jacob-bd

notebooklm-mcp

by jacob-bd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Source Delete

source_delete

Permanently delete sources from a NotebookLM notebook, individually or in bulk. Requires explicit confirmation to prevent irreversible data loss.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be True after user approval
source_idNoSource UUID to delete (single)
source_idsNoList of source UUIDs to delete (bulk, alternative to source_id)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.11.2
    • addedInput schema / properties / confirm / description
      Added value: +"Must be True after user approval"
    • addedInput schema / properties / source_id / description
      Added value: +"Source UUID to delete (single)"
    • addedInput schema / properties / source_ids / description
      Added value: +"List of source UUIDs to delete (bulk, alternative to source_id)"
  2. Changed1 schema field changedv0.9.12
    • changedInput schema / properties / source_ids / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Addedv0.9.1
  4. Removedv0.8.9
  5. Changed3 schema fields changedv0.7.7
    • removedInput schema / properties / confirm / description
      Removed value: -"Must be True after user approval"
    • removedInput schema / properties / source_id / description
      Removed value: -"Source UUID to delete (single)"
    • removedInput schema / properties / source_ids / description
      Removed value: -"List of source UUIDs to delete (bulk, alternative to source_id)"
  6. First observedv0.6.13

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly flags irreversibility and permanence ('IRREVERSIBLE', 'permanently') and the confirmation gate, which are the most important behavioral traits for a delete tool. Minor omissions like cascading effects or auth requirements do not outweigh this transparency.

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 extremely concise: three short, front-loaded statements with zero filler. Every phrase ('permanently', 'IRREVERSIBLE', 'Requires confirm=True') adds meaningful operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The essential context for a destructive tool is present: what it deletes, that it is permanent, and that confirmation is required. However, the schema lists no required parameters, and the description does not clarify that at least one of source_id or source_ids must be provided, nor what happens if both are supplied. The output schema covers return values, but this input ambiguity remains.

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 coverage is 100%, so the schema already documents all three parameters with descriptions. The description adds only marginal value by implying bulk support with 'source(s)' and echoing 'confirm=True', which is already stated in 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 explicitly states the action ('Delete'), the target ('source(s)'), and the critical characteristic ('permanently', 'IRREVERSIBLE'). This makes the tool's destructive purpose unambiguous and distinguishes it from sibling source tools like source_describe, source_rename, or source_get_content.

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?

The description gives a prerequisite ('Requires confirm=True') but does not explicitly say when to use this tool versus alternatives, or that it should only be invoked after explicit user approval. The usage context is implied by the destructive purpose rather than fully stated.

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