Skip to main content
Glama
Sign In

Wandura

by ai.wandura
OverviewDiscussionsAdmin

cinematic_ads_create_project

Create a Cinematic Ads project (free) and, with original_ad_url, load the original ad to remake (MP4 or MOV, up to 3 minutes and 300 MB, any public https URL). Call cinematic_ads_guide first. Cinematic Ads is open to every Wandura account; everything is paid from the project's wallet — the user's own credits for a personal project (paid steps need a paid Wandura plan), the workspace's credits for a workspace project. Flow (the web studio's steps): cinematic_ads_create_project with original_ad_url → cinematic_ads_analyze → poll cinematic_ads_get_project until project.status is 'ready' → optionally cinematic_ads_update_project (brand kit, language, video model), cinematic_ads_brand_scan, cinematic_ads_refine + cinematic_ads_update_asset → cinematic_ads_make_images → cinematic_ads_make_video → poll until production.done is true → cinematic_ads_export → poll until exports[0].status is 'done' and use exports[0].url. Long steps answer {status:'running'} after about a minute and keep going on the server — then poll cinematic_ads_get_project; never start the same step again while it runs.

Input Schema

NameRequiredDescriptionDefault
titleNo
preset_idNoStart from a built-in brand preset (an id from cinematic_ads_list_templates → presets, e.g. preset:langla) when the user names that brand: its app name, icon, mascot, end card and watermark are filled. Check project.brand.preset in the answer (presetApplied false = it was not applied: call cinematic_ads_apply_template {preset_id}).
template_idNoStart from one of the caller's saved templates (cinematic_ads_list_templates). A template with `video` brings its original ad, analysis and cast: the project starts analysed (status ready, no analysis to pay), named after the template unless a title is given — go straight to the assets.
workspace_idNoWorkspace that owns and pays for the project (from cinematic_ads_list_projects). Omit it for a personal project paid from the user's own credits.
original_ad_urlNoPublic https URL of the original ad (MP4/MOV). Can also be set later with cinematic_ads_set_original_ad.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / template_id / description
      Previous value: -"Start from one of the caller's saved templates (cinematic_ads_list_templates)."New value: +"Start from one of the caller's saved templates (cinematic_ads_list_templates). A template with `video` brings its original ad, analysis and cast: the project starts analysed (status ready, no analysis to pay), named after the template unless a title is given — go straight to the assets."
  2. Changed1 schema field changed
    • changedInput schema / properties / preset_id / description
      Previous value: -"Start from a built-in brand preset id from cinematic_ads_list_templates, e.g. preset:langla."New value: +"Start from a built-in brand preset (an id from cinematic_ads_list_templates → presets, e.g. preset:langla) when the user names that brand: its app name, icon, mascot, end card and watermark are filled. Check project.brand.preset in the answer (presetApplied false = it was not applied: call cinematic_ads_apply_template {preset_id})."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond annotations (readOnly=false, openWorld=true, idempotent=false) by disclosing that creation is free, that paid steps require a paid Wandura plan, and that costs come from either the user's credits or the workspace wallet depending on workspace_id. It also discloses the async contract: long steps return {status:'running'} after about a minute and continue server-side.

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 purpose and cost model, then the flow. It is dense and somewhat long, with the full step list arguably duplicating what cinematic_ads_guide could carry, but every sentence conveys routing or polling information an agent needs.

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?

No output schema exists, yet the description names the exact polling fields to check (project.status 'ready', production.done, exports[0].status 'done' and exports[0].url) and maps every downstream sibling. Nothing essential to calling this tool correctly within the pipeline is missing.

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 80%, so baseline is 3, but the description adds value not in the schema: original_ad_url must be MP4/MOV, up to 3 minutes and 300 MB, public https. It also clarifies the payment semantics of workspace_id (owns and pays) versus omitting it for a personal project.

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 ('Create a Cinematic Ads project') and immediately states its distinguishing behavior: optionally loading an original ad for remaking. Sibling tools are named throughout, so an agent can tell this is the pipeline entry point rather than a project mutator or reader.

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?

Explicitly says 'Call cinematic_ads_guide first' and lays out the ordered flow from create → analyze → poll get_project → optional refine/brand steps → make_images/make_video → export, with the exact stopping conditions. It also warns never to re-start the same step while it runs, which is a real usage pitfall.

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

All Wandura toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources