Skip to main content
Glama

notebook_copy

Duplicate a notebook you own — including its sources and Studio artifacts — into a new notebook and return the new notebook's ID and URL.

Instructions

Copy a whole notebook — its sources and Studio artifacts — into a new notebook. RPC-backed. Returns the new notebook id and URL. The sources are copied in the background and may not be listed in the reply yet — call list_sources a few seconds later. Only a notebook you own can be copied (not one shared with you or public). Not idempotent: a failure is never retried automatically, so check the notebook list before retrying.

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": "notebook_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoTitle of the copy. Defaults to "Copy of <source title>".
notebook_idNoNotebook UUID (alternative to notebook_url).
notebook_urlNoNotebookLM notebook URL (the source).

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool payload on success. The exact shape depends on the tool.
errorNoHuman-readable error message, present only when success is false.
successYesWhether the tool call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.11.1

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well: it discloses the async background source copy, the possible incomplete reply, the ownership restriction, and that the operation is not idempotent with no automatic retry. These are exactly the traits an agent needs to avoid misreporting results or double-copying.

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?

Purpose is front-loaded in the first clause, then each subsequent sentence adds one distinct operational fact (return values, async caveat, ownership, idempotency). No filler or repetition.

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?

Outputs are covered by an output schema and the description still summarizes the returned id and URL, while the async-copy caveat, ownership prerequisite, and non-idempotency fill the remaining gaps an agent would otherwise hit. Nothing material is missing for a 3-parameter copy tool.

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%, so all three parameters (title, notebook_id, notebook_url) are already documented, including the default title behavior. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Copy a whole notebook — its sources and Studio artifacts — into a new notebook') and scopes it to whole-notebook copies, which distinguishes it from source_copy and content_copy without naming them. An agent knows immediately what this does and what it does not do.

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

Usage Guidelines4/5

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

Gives a clear prerequisite (only notebooks you own, not shared or public ones) and a post-call follow-up ('call list_sources a few seconds later') plus a retry rule ('check the notebook list before retrying'). It does not explicitly route to sibling copy tools for narrower scopes, but the ownership condition and follow-up steps are concrete guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.