Skip to main content
Glama

get_notebook

Retrieve detailed information about a specific notebook by ID to access its content and metadata for querying and analysis.

Instructions

Get detailed information about a specific notebook by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe notebook ID

Implementation Reference

  • The primary handler function that implements the core logic of the 'get_notebook' tool. It retrieves the notebook by ID from the library, handles errors if not found, and returns the notebook data or an error.
    async handleGetNotebook(args: { id: string }): Promise<ToolResult<{ notebook: any }>> {
      log.info(`🔧 [TOOL] get_notebook called`);
      log.info(`  ID: ${args.id}`);
    
      try {
        const notebook = this.library.getNotebook(args.id);
        if (!notebook) {
          log.warning(`⚠️  [TOOL] Notebook not found: ${args.id}`);
          return {
            success: false,
            error: `Notebook not found: ${args.id}`,
          };
        }
    
        log.success(`✅ [TOOL] get_notebook completed: ${notebook.name}`);
        return {
          success: true,
          data: { notebook },
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        log.error(`❌ [TOOL] get_notebook failed: ${errorMessage}`);
        return {
          success: false,
          error: errorMessage,
        };
      }
    }
  • The tool schema definition for 'get_notebook', specifying the input schema (requires 'id' string) and description used by the MCP protocol.
    {
      name: "get_notebook",
      description: "Get detailed information about a specific notebook by ID",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "The notebook ID",
          },
        },
        required: ["id"],
      },
    },
  • src/index.ts:189-193 (registration)
    The registration/dispatch logic in the main MCP server that maps incoming 'get_notebook' tool calls to the corresponding handler method.
    case "get_notebook":
      result = await this.toolHandlers.handleGetNotebook(
        args as { id: string }
      );
      break;
  • The underlying helper method in NotebookLibrary that performs the actual notebook lookup by ID, used by the tool handler.
    getNotebook(id: string): NotebookEntry | null {
      return this.library.notebooks.find((n) => n.id === id) || null;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions retrieving 'detailed information' but does not specify what that includes, whether it's a read-only operation, error handling, or authentication requirements. This leaves significant gaps for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It does not explain what 'detailed information' includes, potential errors, or how the tool behaves in edge cases. For a tool with no structured behavioral data, more context is needed to guide effective usage.

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?

The input schema has 100% description coverage, clearly documenting the 'id' parameter. The description adds minimal value by implying the ID is used to fetch notebook details, but does not provide additional context like format examples or constraints beyond what the schema already states.

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 clearly states the tool's purpose as retrieving detailed information about a specific notebook using its ID. It specifies the verb ('get') and resource ('notebook'), but does not differentiate it from sibling tools like 'select_notebook' or 'search_notebooks', which may have overlapping functionality.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'list_notebooks' or 'search_notebooks'. It lacks context about prerequisites, exclusions, or specific scenarios where this tool is preferred, leaving the agent to infer usage.

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