Skip to main content
Glama
Sign In
mcp-google

mcp-google

by Antonio-byte10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Baixar item do Estúdio

notebook_estudio_baixar

Downloads a previously generated Studio item by title or id—audio, video, slides, infographic, report, mind map, quiz or table—and saves the files to a local output folder on this PC.

Instructions

Baixa (de novo) um item já gerado no Estúdio pelo título ou id: áudio .m4a, vídeo .mp4, slides (pdf/pptx/imagens + texto), infográfico, e texto de relatório, mapa mental, cartões, teste e tabela. Os arquivos vão SEMPRE para /app/%LOCALAPPDATA%\mcp-google/saidas/notebooklm neste PC.

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": "<notebook>",
      "item": "<item>"
    },
    "name": "notebook_estudio_baixar"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesTítulo (ou parte) ou id do item (veja notebook_estudio).
baixarNoSó para slides. Padrão: pdf.
notebookYesId, URL ou título do notebook (o título pode ser parcial).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.1

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=true) the description discloses the concrete side effect: files are always written to a fixed local path on this PC. It does not address overwrite semantics of the "(de novo)" re-download or any size/rate limits, so it stops short of full disclosure.

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

Conciseness4/5

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

Two dense sentences: the capability and its scope come first, the destination-path constraint second. It earns nearly every clause, though the mixed "/app/%LOCALAPPDATA%\" path rendering is awkward and slightly hard to parse.

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?

With no output schema, the description should cover what the call returns; it explains where files land but not whether the response contains paths, confirmations, or overwrite warnings. For a 3-parameter download tool with a mutation side effect, that leaves a meaningful gap.

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 coverage is 100%, so the baseline is 3. The description does add a little meaning by mapping artifact types to the item parameter and by naming the slide output formats that correspond to the baixar enum, but it gives no format guidance (e.g. pdf_pptx vs imagens).

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 ("Baixa (de novo)") plus the resource and enumerates exactly which Studio artifacts can be fetched (áudio, vídeo, slides, infográfico, relatório, mapa mental, cartões, teste, tabela). The word "já gerado" cleanly separates it from the notebook_gerar_* siblings, though it never names notebook_exportar or notebook_estudio as alternatives.

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?

Usage is implied by "já gerado" (only call after the item exists) and by the pointer to notebook_estudio for ids, but there is no explicit when-to-use/when-not framing or comparison against notebook_exportar, which sounds like the nearest competing option.

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