Skip to main content
Glama

content_copy

Copies Studio artifacts (audio, video, reports, quizzes, slide decks) from an owned notebook into another existing notebook and returns original and copied artifact IDs.

Instructions

Copy Studio artifacts (audio, video, reports, quizzes, slide decks…) into another existing notebook. RPC-backed. Returns, for each artifact, its original id and the id of the copy. 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": {
      "content_ids": "<content_ids>"
    },
    "name": "content_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_idsYesIds of the Studio artifacts to copy (from list_content).
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

A4.2/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 the ownership restriction, that the operation is RPC-backed, that it is not idempotent, and that failures are never retried automatically. It leaves open what happens on partial failure across multiple content_ids, which is the one remaining behavioral gap.

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?

Five short sentences, each carrying distinct information (purpose, mechanism, return value, precondition, idempotency) with the purpose front-loaded. No filler or restatement of the name.

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?

An output schema exists, yet the description still summarizes the return shape (original id plus copy id), which is helpful rather than redundant. Ownership, destination requirement, and retry behavior are all covered; only duplicate handling and partial-failure semantics for multi-id copies are absent.

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 five parameters are already documented, including that notebook_url is the source and target_notebook_id is the destination. The description reinforces the source/destination distinction but adds no format, constraint, or default details beyond the schema — baseline 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?

The description names a specific verb and resource ('Copy Studio artifacts... into another existing notebook') and enumerates artifact types, which separates it from notebook_copy or source_copy. An agent can distinguish it from siblings without opening the schema.

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?

It gives a clear precondition for use: the source must be a notebook you own, not one shared with you or public, and the destination must be an existing notebook. It does not name an alternative tool for the shared/public case, but the when-to-use and when-not conditions are explicit.

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