Skip to main content
Glama

note.create

Add custom notes with markdown formatting to your NotebookLM notebook for saving research findings, summaries, and key insights.

Instructions

Create a note in the NotebookLM Studio panel.

Notes are user-created annotations that appear in your notebook. Use them to save research findings, summaries, key insights, or any custom content you want to keep alongside your sources.

Notes support markdown formatting for rich text content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the note (required)
contentYesContent/body of the note. Supports markdown formatting.
notebook_urlNoNotebook URL. If not provided, uses the active notebook.
session_idNoSession ID to reuse an existing session

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.
Behavior3/5

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

Annotations already indicate readOnlyHint=false (mutation) and idempotentHint=false. The description adds basic context (supports markdown, user-created) but no additional behavioral traits like side effects or auth requirements.

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 concise with three sentences, leading with the main purpose. It avoids unnecessary details and is well-structured.

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?

Given that an output schema exists (though not shown), the description covers the essential purpose and usage. It could mention error conditions or prerequisites but is sufficient for a straightforward create operation.

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?

Schema description coverage is 100%, and the descriptions in the schema adequately explain each parameter. The external description does not add extra meaning beyond the 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?

The description clearly states 'Create a note in the NotebookLM Studio panel' with specific verb and resource. It distinguishes from siblings like note.save_chat and note.to_source by focusing on creating a new note from scratch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains typical use cases (saving research findings, summaries, etc.) but does not provide explicit guidance on when NOT to use it or compare to alternatives.

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