Skip to main content
Glama
Sign In
notebooklm-api

notebooklm-api

by mcpware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_store

Create a document store for uploading files and enabling searchable Q&A with grounded citations via the Gemini File Search API.

Instructions

Create a new document store for uploading and searching files.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
display_nameNoHuman-readable name for the store (e.g. "Legal Documents Q1")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that a store is created; it does not cover what happens when display_name is omitted, whether creation is idempotent, permissions needed, or what the response contains.

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 one succinct sentence with no filler. The core action and purpose are front-loaded, making it instantly understandable.

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

Completeness3/5

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

The description is adequate for a simple creation tool, but it does not mention whether the call returns a store ID or how the result connects to siblings like upload_document and ask. In an annotation-free context, those gaps are noticeable.

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 already fully describes display_name with a useful human-readable example, so schema coverage is 100%. The description adds no additional parameter-level meaning, making the baseline of 3 appropriate.

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 states a specific verb ('Create') and resource ('document store') and clarifies its purpose ('for uploading and searching files'). This clearly differentiates it from siblings like delete_store and list_stores.

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 implies that creating a store is a prerequisite for uploading files, but it never explicitly states when to use this tool or mentions alternatives. No exclusion conditions or sibling routing is provided.

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