Skip to main content
Glama

cinematic_ads_duplicate_project

Make 1 to 5 copies of a project as it is now, in the same workspace: the original ad, its analysis, the cast and places (images, modes, descriptions), the clip plan, the settings and the final-video choices it last built with. Each copy is a new project with its own id and is already analysed, so it goes on at step 4 — e.g. give one person a different photo in each copy (cinematic_ads_update_asset with that copy's asset ids from cinematic_ads_get_project). Copies are named " (copy n)". Never a clip take, a fix or a final video. Refused while the project is being analysed. Free.

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": {
      "project_id": "<project_id>",
      "count": "<count>"
    },
    "name": "cinematic_ads_duplicate_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesHow many copies, 1 to 5. Near the hourly limit on new projects only the copies it still allows are made (limited: true).
project_idYesThe project to copy, from cinematic_ads_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses that copies are new projects with their own ids, that they arrive already analysed and resume at step 4, the naming convention '<name> (copy n)', the analysis-in-progress refusal, and that the operation is free. It also implicitly explains non-idempotency (each call yields fresh copies) and defers partial-limit behavior to the schema.

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 payload, then constraints and an example. Dense but every sentence carries information; the parenthetical example is useful but slightly bulky relative to the rest.

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?

With no output schema, the description implicitly covers return semantics (new project ids, generated copy names) and the refusals/limits, which is enough to call it correctly. It stops short of stating the exact shape of the response (e.g., a list of new project ids and the 'limited' flag).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description still adds meaningful semantics: copies are independent entities with separate asset ids, which explains what 'count' actually produces and motivates the multi-copy use case in the example.

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 ('Make 1 to 5 copies of a project as it is now, in the same workspace') and enumerates exactly what is carried over (ad, analysis, cast/places, clip plan, settings, final-video choices). This clearly separates it from create_project, save_template, and clone_template siblings.

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?

Explicit exclusions are given ('Never a clip take, a fix or a final video') plus a precondition ('Refused while the project is being analysed') and a concrete follow-up workflow routing to cinematic_ads_update_asset with ids from cinematic_ads_get_project. The agent knows when to pick this and when not to.

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