Skip to main content
Glama

Duplicate Project

projects_duplicate
Idempotent

Duplicate a project with shared source media and copied timeline, captions, settings and framing. Returns clip_id for copied clip projects. Reuse idempotencyKey only with identical inputs.

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": {
      "projectId": "<projectId>",
      "workspaceId": "<workspaceId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "projects_duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
projectIdYesUUID string.
workspaceIdYes
idempotencyKeyYes
projectFolderIdNo

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
statusYes
clip_idYes
series_idYes
created_atYes
updated_atYes
descriptionYes
aspect_ratioYes
thumbnail_urlNo
mutationReceiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-destructive and idempotent=true, so the bar is lower, but the description earns credit by pinning down what 'shared source media' means (media referenced, not copied) and by making the idempotentHint concrete: same key with different inputs is not safe. It still doesn't say what permissions the duplication requires or how long a large duplication takes.

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?

Three tightly packed sentences with the core action front-loaded and no filler. The clip_id sentence is slightly terse to the point of ambiguity about what a 'clip project' is, but it is not wasted space.

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?

An output schema exists, so return-value detail is not required, and the description correctly focuses on duplication semantics. For a 5-parameter mutation with only 20% schema description coverage, though, the naming and folder-placement behavior of the new project is left entirely undocumented.

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 only 20% across 5 parameters, so the description would need to compensate. It explains idempotencyKey semantics well but says nothing about name (e.g. whether omission produces a 'Copy of' default), workspaceId's nullability, or where projectFolderId places the duplicate.

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 (duplicate a project) and immediately enumerates what is duplicated: shared source media, timeline, captions, settings, framing. That level of detail distinguishes it from projects_create and from sibling clone-style tools without needing 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 Guidelines3/5

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

The idempotencyKey reuse rule ('only with identical inputs') is genuine usage guidance, and the clip-project return note signals a special case. However, there is no explicit when-to-use versus projects_create, and no statement of preconditions such as whether the caller must own or have access to the source project.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources