Skip to main content
Glama
Sign In
notebooklm

notebooklm

by dfelix-net
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_slide_deck

Create a complete slide presentation from a NotebookLM notebook ID. Add optional instructions to tailor the deck's content.

Instructions

Gera uma apresentação de slides no NotebookLM.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "notebook_id": "<notebook_id>"
    },
    "name": "generate_slide_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
notebook_idYes
instructionsNoCrie uma apresentação de slides completa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the entire behavioral burden, and it discloses almost nothing: not whether generation is async/long-running, whether it overwrites existing decks, what permissions are needed, or what the result looks like. The only contextual hint is that it operates 'in NotebookLM'.

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

Conciseness3/5

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

A single short sentence is appropriately front-loaded and contains no filler, but it is under-specified rather than genuinely concise — the brevity reflects missing information rather than tight editing.

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?

For a generation tool with no annotations, no output schema, and zero parameter documentation, the description is far too thin. An agent cannot tell what inputs to shape, what the call returns, or how long it takes; only the high-level purpose is conveyed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there are two parameters, yet the description says nothing about notebook_id (required) or instructions (with its default). It does not compensate for the documentation gap at all.

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 gives a specific verb ('Gera') and resource ('apresentação de slides') scoped to NotebookLM, which cleanly separates it from siblings like generate_mind_map or generate_quiz. It does not, however, explicitly differentiate itself from the other generate_* tools beyond the resource noun.

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?

There is no guidance on when to use this tool versus the many sibling generators, no prerequisites (e.g. whether a notebook must already exist), and no mention of when a slide deck is the appropriate output. Usage must be fully inferred.

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