Skip to main content
Glama

source_copy

Copy selected sources from an owned notebook into an existing target notebook and return each original source ID with its new copy ID.

Instructions

Copy some of a notebook’s sources into another existing notebook. RPC-backed. Returns, for each source, its original id and the id of the copy. The target must be named explicitly. Only from a notebook you own (not one shared with you or public). Not idempotent: a failure is never retried automatically.

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": {
      "source_ids": "<source_ids>"
    },
    "name": "source_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idsYesIds of the sources to copy (from list_sources).
notebook_idNoNotebook UUID (alternative to notebook_url).
notebook_urlNoNotebookLM notebook URL (the source).
target_notebook_idNoUUID of the notebook to copy into. Required (or target_notebook_url).
target_notebook_urlNoURL of the notebook to copy into (alternative to target_notebook_id).

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

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses RPC backing, non-idempotency, the absence of automatic retry on failure, and an ownership restriction on the source notebook. Missing: permission requirements on the target notebook and whether partial failures leave a partial copy.

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?

Five short sentences, front-loaded with the action, then constraints, then failure semantics. Every sentence carries information, though the return-id sentence partially duplicates the existing output schema.

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

Completeness4/5

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

For a 5-parameter mutation tool with an output schema but no annotations, the description covers the key risks (non-idempotent, no retry, ownership restriction) so an agent can call it safely. Remaining gaps are small: target-side permissions and partial-failure behavior.

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 both id and URL variants for source and target are already documented. The description only adds that the target 'must be named explicitly', which reinforces rather than extends the schema. Baseline 3 is appropriate.

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 and resource with scope: 'Copy some of a notebook's sources into another existing notebook.' This clearly distinguishes it from whole-notebook copying, though it never names the sibling (notebook_copy/content_copy) that handles the broader case, so an agent must infer the boundary.

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 an explicit precondition — 'Only from a notebook you own (not one shared with you or public)' — and restates that the target must be named explicitly. It does not state when to prefer this over content_copy or notebook_copy, so alternatives remain an inference.

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