Skip to main content
Glama

list_notebooks

Retrieve available library notebooks with metadata to select appropriate sources for AI-powered document queries and synthesized responses.

Instructions

List all library notebooks with metadata (name, topics, use cases, URL). Use this to present options, then ask which notebook to use for the task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_notebooks' tool. It logs the call, retrieves notebooks from the library, and returns them in a standardized ToolResult format, with error handling.
     * Handle list_notebooks tool
     */
    async handleListNotebooks(): Promise<ToolResult<{ notebooks: any[] }>> {
      log.info(`🔧 [TOOL] list_notebooks called`);
    
      try {
        const notebooks = this.library.listNotebooks();
        log.success(`✅ [TOOL] list_notebooks completed (${notebooks.length} notebooks)`);
        return {
          success: true,
          data: { notebooks },
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        log.error(`❌ [TOOL] list_notebooks failed: ${errorMessage}`);
        return {
          success: false,
          error: errorMessage,
        };
      }
    }
  • The input/output schema definition for the 'list_notebooks' tool, part of the notebookManagementTools array. It has no required input parameters.
    {
      name: "list_notebooks",
      description:
        "List all library notebooks with metadata (name, topics, use cases, URL). " +
        "Use this to present options, then ask which notebook to use for the task.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • The underlying library method called by the handler, which simply returns the array of notebooks from the stored library data.
    listNotebooks(): NotebookEntry[] {
      return this.library.notebooks;
    }
  • src/index.ts:185-187 (registration)
    The dispatch case in the main MCP tool execution switch statement that routes 'list_notebooks' calls to the appropriate handler method.
    case "list_notebooks":
      result = await this.toolHandlers.handleListNotebooks();
      break;
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the operation (listing with metadata) and suggests a workflow (present options then ask), but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, or error conditions. It adds some context but lacks operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero waste. The first sentence states purpose and output, the second provides usage guidance. Every word earns its place, and information is front-loaded appropriately.

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 zero parameters, no annotations, and no output schema, the description provides good context about what the tool does and how to use it. However, it doesn't describe the return format (structure of metadata) or potential limitations (e.g., maximum results), leaving some gaps for a list operation.

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 tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to add parameter information, so it appropriately focuses on usage guidance. A baseline of 4 is appropriate for zero-parameter tools when the schema is fully documented.

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 the verb ('List') and resource ('all library notebooks'), specifies the metadata returned (name, topics, use cases, URL), and distinguishes from siblings like 'get_notebook' (single notebook) and 'search_notebooks' (filtered search). It provides specific, actionable information beyond just restating the name.

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?

Explicitly states when to use this tool ('to present options, then ask which notebook to use for the task') and implies when not to use it (when you already know which notebook to target, use 'get_notebook' instead). It provides clear context for agent decision-making.

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/inventra/notebooklm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server