Skip to main content
Glama

cinematic_ads_update_project

DestructiveIdempotent

Change a Cinematic Ads project's settings: title, aspect, resolution, target language, video model and the brand kit (app name, call to action, app icon, mascot, end card, frames, app screens, the user's brief). Free. Image and video URLs may be any public https URL. Refused while an analysis runs; the video model cannot change once part of the video is made (start a new project for another model).

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>"
    },
    "name": "cinematic_ads_update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoBrand kit. Every field optional; image/video URLs may be any public https URL (copied to Wandura storage).
titleNo
aspectNo
dialogueNoHow the original ad's lines become the remake's: keep_english (the default — a line spoken in English stays in English, only the others are translated: for ads that teach English) or translate_all (every line said in targetLanguage). Same timing rule as targetLanguage.
project_idYesProject id from cinematic_ads_list_projects or cinematic_ads_create_project.
resolutionNo
videoModelNoThe video model: wandura-0-1 = Wandura 0.1 (new projects start on it; the lowest cost), dreamina-seedance-2-5-ref = Seedance 2.5, dreamina-seedance-2-ref = Seedance 2.0.
targetLanguageNoLanguage code of the remake's speech and captions (e.g. en, vi, es-MX), or 'source' to keep the original ad's. Set it before cinematic_ads_analyze (the new cast is designed for it); it can still change until the video is being made (then the clips are written again), not after.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / dialogue
      Added value: +{
      +  "description": "How the original ad's lines become the remake's: keep_english (the default — a line spoken in English stays in English, only the others are translated: for ads that teach English) or translate_all (every line said in targetLanguage). Same timing rule as targetLanguage.",
      +  "enum": [
      +    "keep_english",
      +    "translate_all"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / targetLanguage / description
      Previous value: -"Language code of the remake's speech and captions (e.g. en, vi, es-MX), or 'source' to keep the original ad's."New value: +"Language code of the remake's speech and captions (e.g. en, vi, es-MX), or 'source' to keep the original ad's. Set it before cinematic_ads_analyze (the new cast is designed for it); it can still change until the video is being made (then the clips are written again), not after."
  2. Changed1 schema field changed
    • changedInput schema / properties / videoModel / description
      Previous value: -"Wandura 0.1 (default for new projects, cheapest, clips up to 30 s), Seedance 2.5 (clips up to 30 s) or Seedance 2.0 (clips up to 15 s)."New value: +"The video model: wandura-0-1 = Wandura 0.1 (new projects start on it; the lowest cost), dreamina-seedance-2-5-ref = Seedance 2.5, dreamina-seedance-2-ref = Seedance 2.0."
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already supply destructiveHint, idempotentHint and openWorldHint, so the description only needs to add timing and lifecycle context — and it does: cost ('Free'), refusal during analysis, and the point of no return on the video model. It does not clarify what happens to omitted fields or to already-generated clips, which is the remaining unknown for a destructive update.

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 sentences, front-loaded with purpose, then cost, then constraints — a sensible order with no filler. The long parenthetical enumerating brand-kit fields is slightly heavy but each item earns its place by defining the mutation's scope.

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?

For a destructive, multi-field update tool with no output schema and annotations already carrying safety hints, the description supplies the missing operational context: cost, the analysis lock, and the irreversibility of the video model. An agent has enough to decide when to call it and what to warn the user about.

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 63% and the description largely restates the schema's property list, though it does usefully frame the brand-kit fields as a single group (app name, CTA, icon, mascot, end card, frames, screens, brief). Parameters not covered by either source — notably 'pronunciation' and 'dialogue' — get no help here. Adequate but not additive beyond the schema.

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?

Opens with a specific verb+resource ('Change a Cinematic Ads project's settings') and then enumerates exactly which settings, including the full brand kit. An agent can distinguish this project-level mutation from siblings like cinematic_ads_update_asset or cinematic_ads_update_clip without opening any 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?

Gives concrete when-not conditions: refused while an analysis runs, and the video model is frozen once part of the video is made, with the explicit alternative 'start a new project for another model'. No routing to the update_asset/update_clip siblings for their respective scopes, which is the only gap.

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