Skip to main content
Glama

auth_setup

Authenticate with Google to access NotebookLM. Opens a browser window for manual login and returns immediately; use the get_health tool to verify successful authentication.

Instructions

Google authentication for NotebookLM access - opens a browser window for manual login to your Google account. Returns immediately after opening the browser. You have up to 10 minutes to complete the login. Use 'get_health' tool afterwards to verify authentication was saved successfully. Use this for first-time authentication or when auto-login credentials are not available. IMPORTANT: If already authenticated, this tool will skip re-authentication. For switching accounts or rate-limit workarounds, use 're_auth' tool instead.

TROUBLESHOOTING for persistent auth issues: If setup_auth fails or you encounter browser/session issues:

  1. Ask user to close ALL Chrome/Chromium instances

  2. Run cleanup_data(confirm=true, preserve_library=true) to clean old data

  3. Run setup_auth again for fresh start This helps resolve conflicts from old browser sessions and installation data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
show_browserNoShow browser window (simple version). Default: true for setup. For advanced control, use browser_options instead.
browser_optionsNoOptional browser settings. Control visibility, timeouts, and stealth behavior.

Output Schema

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

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

The description adds significant context beyond annotations: it opens a browser, returns immediately, allows 10 minutes for login, and skips if already authenticated. Annotations (readOnlyHint=false, idempotentHint=false) are consistent. No contradiction. Includes troubleshooting steps for persistent issues.

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?

Description is longer than ideal but well-structured: clear purpose, usage guidance, and a separate troubleshooting section. Every sentence adds value. Could be slightly trimmed, but overall efficient.

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 presence of output schema (not shown) and comprehensive annotations, the description completely covers purpose, usage, parameters, and troubleshooting. No gaps for an agent to select and invoke correctly.

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?

Input schema has 100% coverage. The description adds value by explaining default behavior for 'show_browser' and 'browser_options' (e.g., default true for setup, headless false). It clarifies the simple vs advanced control distinction, aiding agent in choosing 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 clearly identifies the tool as setting up Google authentication for NotebookLM by opening a browser for manual login. It distinguishes from the 're_auth' sibling tool, explicitly stating when to use each.

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?

The description provides explicit guidance: use for first-time auth or when auto-login is unavailable; skip re-auth if already authenticated; recommend using 'get_health' to verify. It also specifies alternative tool 're_auth' for switching accounts or rate-limit workarounds.

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