Skip to main content
Glama
roomi-fields

notebooklm-mcp

by roomi-fields
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

auth_switch

Re-authenticate or switch Google accounts when NotebookLM rate limits are hit or auth fails. Resets browser sessions and credentials for a fresh login.

Instructions

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

  • NotebookLM rate limit is reached (50 queries/day for free accounts)

  • 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

TableJSON 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

TableJSON 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.

Tool Definition Quality

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, etc.), the description details destructive actions: 'Close all active browser sessions', 'Delete all saved authentication data (cookies, Chrome profile)', and adds post-verification steps. This is rich behavioral context.

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?

The description is well-structured with bullets for use cases and steps, and it front-loads the purpose. It's slightly long due to troubleshooting, but each section adds practical value.

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?

Given the tool's destructive and browser-interactive nature, the description covers when to use, what happens, side effects, verification, and troubleshooting. With an output schema present, return value explanation is not required.

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?

The schema covers 100% of parameters, each with descriptions. The tool description adds nothing about parameters, so the baseline of 3 for high schema coverage 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 description opens with a clear verb and resource: 'Switch to a different Google account or re-authenticate.' It also lists three specific use cases, which distinguishes it from siblings like auth_setup and auth_logout.

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?

It explicitly states 'Use this when:' with three concrete scenarios, and provides a post-condition ('use get_health to verify'). However, it doesn't explicitly name alternatives or provide 'when not' guidance, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/roomi-fields/notebooklm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server