Skip to main content
Glama
Sign In
research-hub

research-hub

by WenyuChiou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

notebooklm_generate

Trigger NotebookLM artifact generation for a cluster notebook to produce summaries or briefs.

Instructions

Trigger NotebookLM artifact generation for a cluster notebook.

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": {
      "cluster_slug": "<cluster_slug>"
    },
    "name": "notebooklm_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_slugYes
artifact_typeNobrief
headlessNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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 must convey behavioral traits. It only says 'Trigger... generation' without indicating whether the operation is destructive, asynchronous, or requires specific permissions. The agent cannot anticipate side effects or state changes.

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?

The description is a single sentence, which is concise but lacks necessary detail. It is front-loaded but too brief for a 3-parameter tool with no schema descriptions.

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 complexity of sibling tools and lack of schema descriptions, the description is incomplete. It does not clarify what 'artifact generation' entails, how it differs from similar tools, or what the output schema provides.

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?

With 0% schema description coverage, the description must explain parameters. It does not mention cluster_slug, artifact_type, or headless at all. The agent has no semantic guidance beyond parameter names and types.

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 verb 'Trigger' and the resource 'NotebookLM artifact generation for a cluster notebook'. It is specific but does not differentiate from siblings like notebooklm_bundle or compose_brief_draft. The purpose is clear at a high level.

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?

No guidance on when to use this tool versus alternatives (e.g., compose_brief_draft, notebooklm_bundle). There is no mention of prerequisites or typical use cases, leaving the agent to infer from the name alone.

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