Skip to main content
Glama
jacob-bd

notebooklm-mcp

by jacob-bd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Source Sync Drive

source_sync_drive

Identify stale Google Drive sources and refresh their content by syncing selected source IDs after user approval.

Instructions

Sync Drive sources with latest content. Requires confirm=True.

Call source_list_drive first to identify stale sources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be True after user approval
source_idsYesSource UUIDs to sync

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.2
    • addedInput schema / properties / confirm / description
      Added value: +"Must be True after user approval"
    • addedInput schema / properties / source_ids / description
      Added value: +"Source UUIDs to sync"
  2. Changed3 schema fields changedv0.9.12
    • addedInput schema / properties / source_ids / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • removedInput schema / properties / source_ids / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / source_ids / type
      Removed value: -"array"
  3. Addedv0.9.5
  4. Removedv0.9.1
  5. Addedv0.9.1
  6. Removedv0.8.9
  7. Changed2 schema fields changedv0.7.7
    • removedInput schema / properties / confirm / description
      Removed value: -"Must be True after user approval"
    • removedInput schema / properties / source_ids / description
      Removed value: -"Source UUIDs to sync"
  8. First observedv0.6.13

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose a required confirmation flag and a prerequisite workflow, which is useful. However, it does not explain what 'sync' actually changes, whether it is destructive or reversible, or any permission/auth requirements.

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: two short sentences that state the action, the mandatory flag, and the prerequisite call. Every sentence earns its place and the critical information is front-loaded.

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?

With no annotations, the description is reasonably complete for a two-parameter tool with an output schema. It covers the confirmation requirement and the prerequisite listing step, but it omits any explanation of sync side effects, permissions, or what happens to existing content, leaving some ambiguity for an agent.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents both parameters. The description adds meaningful context by linking source_ids to the output of source_list_drive and emphasizing that confirm must be true, enriching the agent's understanding of how to populate and invoke the parameters.

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 states a specific verb and resource: 'Sync Drive sources with latest content.' This clearly identifies the action and distinguishes it from sibling tools like source_list_drive or source_get_content, especially by referencing the listing tool as a prerequisite.

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 gives explicit usage guidance: 'Requires confirm=True' and 'Call source_list_drive first to identify stale sources.' This tells the agent when and how to prepare, but it does not explicitly state when not to use this tool or mention alternative tools for similar operations.

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