Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GOOGLE_CLIENT_IDYesYour Google Cloud OAuth2 client ID
GOOGLE_CLIENT_SECRETYesYour Google Cloud OAuth2 client secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
notebooklm_validate_metadataC

Validate metadata against schema

notebooklm_get_metadataC

Get metadata for a notebook or source

notebooklm_set_metadataC

Set metadata for a notebook or source

notebooklm_query_metadataC

Query notebooks or sources by metadata

notebooklm_list_notebooksA

List recently viewed notebooks

notebooklm_get_notebookB

Get notebook details with sources

notebooklm_create_notebookC

Create a new notebook

notebooklm_delete_notebookC

Delete notebook(s)

notebooklm_share_notebookB

Share notebook with a user

notebooklm_add_sourcesB

Add sources to a notebook

notebooklm_get_sourceC

Get source details

notebooklm_remove_sourcesB

Remove sources from a notebook

notebooklm_generate_audioC

Generate audio overview for a notebook

notebooklm_delete_audioC

Delete audio overview

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct resource-action combination: metadata operations are clearly separated into validate/get/set/query, notebook operations into list/get/create/delete/share, and sources/audio each have their own dedicated tools. Even get_notebook and get_source are unambiguous because one returns notebook details with sources and the other returns a specific source's details.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern with the notebooklm_ prefix. Action verbs such as get, set, list, create, delete, add, remove, generate, and share are used predictably across the tool set.

Tool Count5/5

14 tools is well within the ideal range for a domain-specific MCP server. The count covers notebooks, sources, metadata, sharing, and audio without feeling bloated or thin.

Completeness4/5

The tool surface provides strong lifecycle coverage for notebooks, sources, metadata, and audio overviews. Minor gaps exist such as no explicit notebook update/rename operation, no standalone list-sources tool, and no unshare or list-audio tools, but these are workable gaps rather than critical dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues