Skip to main content
Glama
roomi-fields

notebooklm-mcp

by roomi-fields
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

auth_switch

Switch Google accounts or start fresh authentication when usage limits are reached or login breaks. Clears saved cookies and browser sessions, then opens a new login window.

Instructions

Switch to a different Google account or re-authenticate. Use this when:

  • NotebookLM usage limit is reached (compute-based, refreshes every 5 hours)

  • You want to switch to a different Google account

  • Authentication is broken and needs a fresh start

This will:

  1. Close all active browser sessions

  2. Delete all saved authentication data (cookies, Chrome profile)

  3. Open browser for fresh Google login

After completion, use 'get_health' to verify authentication.

TROUBLESHOOTING for persistent auth issues: If re_auth fails repeatedly:

  1. Ask user to close ALL Chrome/Chromium instances

  2. Run cleanup_data(confirm=false, preserve_library=true) to preview old files

  3. Run cleanup_data(confirm=true, preserve_library=true) to clean everything except library

  4. Run re_auth again for completely fresh start This removes old installation data and browser sessions that can cause conflicts.

Input Schema

NameRequiredDescriptionDefault
headlessNoAlias/inverse of show_browser: headless=false opens a visible window, headless=true runs hidden. Ignored if show_browser is set.
show_browserNoShow browser window (simple version). Default: true for re-auth. For advanced control, use browser_options instead.
browser_optionsNoOptional browser settings. Control visibility, timeouts, and stealth behavior.

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool payload on success. The exact shape depends on the tool.
errorNoHuman-readable error message, present only when success is false.
successYesWhether the tool call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / headless
      Added value: +{
+  "description": "Alias/inverse of show_browser: headless=false opens a visible window, headless=true runs hidden. Ignored if show_browser is set.",
+  "type": "boolean"
+}
  2. Addedv2.0.4

TDQS

A4.3/5.0
Behavior3/5

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

The description goes well beyond the annotations by disclosing that all browser sessions are closed and all saved authentication data (cookies, Chrome profile) is deleted — critical destructive context that readOnlyHint=false alone does not convey. However, it never states that this requires interactive user action in the browser (a blocking, non-automatable step) or how long the operation takes, which is essential behavioral information for an agent deciding whether to call it mid-task.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The 'This will:' numbered list is front-loaded and earns its place, but the troubleshooting block is long and references tool names that do not exist in the sibling list ('re_auth' vs. auth_switch, 'cleanup_data' vs. server_cleanup), which adds tokens without reliably helping the agent route correctly.

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

Completeness5/5

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

With an output schema present, the description needn't explain return values, and it covers triggers, destructive effects, the interactive login requirement, the verification step, and a recovery path. An agent has enough to decide and act.

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%, with headless, show_browser, and the nested browser_options all documented including precedence rules ('Ignored if show_browser is set'). The description adds nothing about parameters, but the schema fully carries that burden, so the baseline applies.

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 first sentence states a specific verb and resource — switch Google account or re-authenticate — and the bullet list names concrete triggering conditions (usage limit, account switch, broken auth). This is clearly distinguishable from auth_setup and auth_logout among the siblings.

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

Usage Guidelines5/5

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

Explicit 'Use this when:' conditions are given, along with a follow-up verification step ('use get_health') and a fallback path via cleanup_data when re-auth fails repeatedly. Alternatives and their selection conditions are named rather than left to inference.

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