Skip to main content
Glama
Sign In
mcp-google

mcp-google

by Antonio-byte10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Exportar item do Estúdio para o Google Drive

notebook_exportar

Exports generated Studio items to Google Drive and returns a link, sending reports to Docs or Sheets, data tables to Sheets, and slides to Google Slides.

Instructions

Exporta um item já gerado no Estúdio para o Google Drive da conta e devolve o link: relatório (formato documento) → Google Docs ou Planilhas; tabela de dados → Planilhas (os dois pelo próprio NotebookLM, ~5-15 s); slides → Google Apresentações (o NotebookLM não oferece: o MCP baixa o .pptx, envia ao Drive, converte com 'Salvar como apresentação Google' e manda o .pptx enviado para a lixeira do Drive; ~40-60 s). No Claude Desktop os slides podem voltar 'em andamento': chame de novo com os MESMOS dados, que continua de onde parou (não envia de novo o que já foi). Relatório interativo, áudio, vídeo, mapa, cartões e teste não têm exportação para o Google. Cada exportação concluída cria um arquivo NOVO no Drive (pasta Meu Drive): não repita para o mesmo item sem o usuário pedir.

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_exportar"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesTítulo (ou parte) ou id do item (veja notebook_estudio).
destinoNodocs (Google Docs), planilhas (Google Planilhas) ou apresentacoes (Google Apresentações, só slides). Padrão: planilhas para tabela, apresentacoes para slides, docs para relatório.
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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/external-service nature is known. The description adds genuinely useful side effects beyond that — a NEW file is created in My Drive, and for slides the .pptx is uploaded and then sent to the Drive trash — plus timing expectations (~5-15 s vs ~40-60 s). It does not state permission/scope requirements or what happens if the Drive quota or auth fails.

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?

Front-loaded with the core action and return value, then progressively adds per-type detail; nearly every clause earns its place (timings, retry semantics, new-file warning). The parenthetical slide pipeline is dense but is the one place deep detail is warranted.

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

Completeness5/5

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

For a 3-parameter tool with no output schema, the description supplies the return value (a Drive link), the supported/unsupported item matrix, cost in time, side effects, and idempotent retry behavior. An agent has everything needed to call it correctly once.

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% and the destino enum already documents the three values, their defaults per item type, and the 'só slides' restriction. The description's per-type destination mapping largely restates that, adding little new parameter meaning beyond the schema baseline.

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+resource: exports an already-generated Studio item to the account's Google Drive and returns the link, with per-item-type destination mapping. It implicitly separates itself from the notebook_gerar_* family (it exports, it does not generate), but never names the closest sibling notebook_estudio_baixar, so the agent must infer why it would pick Drive export over a local download.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly enumerates what can be exported and, more valuably, what cannot (interactive report, audio, video, map, cards, quiz have no Google export), which prevents misinvocation. It also gives a concrete retry rule for the 'in progress' slides case and warns against repeating exports without user request.

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