Skip to main content
Glama
Sign In
notebooklm-mcp

notebooklm-mcp

by jacob-bd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Refresh Auth

refresh_auth

Reload auth for the requested profile without switching the active account.

Instructions

Reload auth for the requested profile without switching the active account.

Call this after running nlm login to pick up new tokens, or attempt headless recovery with the profile's saved browser. An explicit profile does not switch the MCP server's active account.

Returns status indicating if tokens were refreshed successfully.

Input Schema

NameRequiredDescriptionDefault
profileNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.6
    • addedInput schema / properties / profile
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  2. Addedv0.9.5
  3. Removedv0.8.9
  4. First observedv0.6.13

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses that the active account is not switched, that headless recovery via saved browser may occur, and that status reports refresh success. It stops short of describing failure modes or auth prerequisites, but the key side-effect/disclosure is explicit.

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?

Front-loads the core action and caveat, then lists usage triggers; sentences mostly earn their place. Slightly redundant that the 'does not switch active account' idea appears in both sentence one and sentence three, but the reinforcement is defensible for a subtle auth distinction.

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

Completeness4/5

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

An output schema exists, so the description needn't detail return values beyond noting it reports refresh status. Between the usage triggers and the non-switching caveat, an agent has enough to call it correctly; only auth prerequisites/failure handling are left implicit.

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?

The schema has 0% description coverage on the single optional `profile` param, so the description compensates by tying it to a 'requested profile' and clarifying it does not switch the active account. That adds real meaning beyond the bare string|null schema.

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?

States a specific verb+resource (reload auth) and immediately scopes it (requested profile, without switching the active account). This distinguishes it cleanly from the sibling save_auth_tokens, which is about persisting tokens rather than reloading them.

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?

Gives concrete triggers: call after running `nlm login` to pick up new tokens, or attempt headless recovery with the profile's saved browser. It also names an exclusion (an explicit profile does not switch the active account), so the agent knows this is not an account-switching tool.

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