Skip to main content
Glama
Sign In
nblm-mcp

nblm-mcp

by Diego-Dev-Moros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

download_artifact

Save a completed Studio artifact from a NotebookLM notebook to a file on the server host, using its notebook and artifact IDs.

Instructions

Download a completed Studio artifact to a file on the server host.

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>",
      "artifact_id": "<artifact_id>"
    },
    "name": "download_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifact_idYesThe artifact to download, from list_artifacts.
notebook_idYesThe notebook holding the artifact.
output_pathNoDestination path. A bare filename lands in the configured download directory; omit it to name the file after the artifact.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the key behavioral trait that the file is written to the server host rather than returned to the caller, but says nothing about overwrite behavior, required permissions, or error handling for incomplete artifacts.

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?

A single front-loaded sentence with no filler; the action and destination are both established immediately.

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?

An output schema exists, so return values need no explanation, and the parameters are fully documented. However, for a tool with no annotations that writes a file to a host, the description omits permission requirements and overwrite semantics, leaving gaps an agent would want covered.

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?

Schema description coverage is 100%, and output_path's path-resolution rules are already documented in the schema. The description adds only the 'server host' framing, so the baseline 3 applies.

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?

States a specific verb (Download) and resource (Studio artifact) plus the destination (a file on the server host). It clearly separates itself from list_artifacts and generate_artifact, though it never names a sibling explicitly.

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 word 'completed' hints that only finished artifacts are downloadable, but there is no explicit when-to-use, prerequisite, or alternative (e.g., list_artifacts to find the artifact) guidance. Usage must be 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