Gemini Notebook by Chryzalide (agy-gemini-notebook-plugin)

notebook_login

Connect a Gemini Notebook session by importing signed-in browser cookies or running Google Cloud OAuth, avoiding Playwright sign-in automation.

Instructions

Connect your Gemini Notebook session without Playwright sign-in automation on accounts.google.com.

- Default (`browser_cookies='auto'` or `'chrome'`, `'brave'`, `'firefox'`, `'edge'`, `'chromium'`):
  Imports your already-signed-in `notebooklm.google.com` session directly from your installed
  browser in ~1 second (Engine 2 — unofficial community RPC bridge).
- `gcloud=True`: Runs official `gcloud auth login` OAuth 2.0 flow for Google Cloud Discovery
  Engine `v1alpha` (Engine 1 — 100% official Google Cloud API).
- `open_system_browser=True`: Opens `https://notebooklm.google.com/` in your genuine OS default
  browser so you can verify you are signed in before connecting.

Input Schema

Name	Required	Default
`fresh`	No
`gcloud`	No
`account`	No
`browser`	No	auto
`timeout`	No
`browser_cookies`	No	auto
`open_system_browser`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

A3.6/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 behavioral burden and discloses important traits: browser-cookie import versus official gcloud OAuth, the unofficial community RPC bridge versus official Google Cloud API, and that open_system_browser opens the OS default browser. It still omits behavior for fresh, account, browser, and timeout.

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 front-loaded and organized into clear mode-based bullets. It is somewhat verbose in naming engine internals, but the structure makes the primary modes easy to scan.

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 output schema exists, so return values need not be described. However, for a seven-parameter authentication tool with no annotations and zero schema descriptions, the description is only partially complete because several parameters and their effects are unexplained.

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

Parameters2/5

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

Schema description coverage is 0% across seven parameters, so the description must compensate. It explains gcloud, browser_cookies, and open_system_browser, but leaves fresh, account, browser, and timeout undocumented, and it does not clarify the distinction between browser and browser_cookies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: connect a Gemini Notebook session. It distinguishes authentication from Playwright sign-in automation, and it is obviously distinct from the notebook_* operational siblings, though it does not explicitly name or contrast them.

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 explains the default browser-cookie mode, the gcloud OAuth mode, and the open_system_browser verification mode. It does not explicitly say when this tool must be called versus notebook_status or other siblings, but the authentication context is clear.

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