ava11.1 KB
View saved version →
---
name: ava
description: Use Ava Studio to research references, clone videos or photo carousels, manage campaigns and brand media, continue saved project conversations, generate media, and edit or export projects through its hosted MCP tools.
---
# Ava Studio workflows
Use the connected Ava tools and the user's own account. `whoami` shows brands,
the credit balance, and the connection's monthly budget. The available tool
list reflects granted scopes. If a tool is missing, explain the needed
permission; never ask the user to paste credentials into chat.
## Choose the planning workflow first
Start with `whoami` and the brand context. Carry the app/product summary, audience,
goal, reference links and supplied assets into the selected workflow.
- **The user asks to use a campaign:** reuse the selected campaign with
`campaign_list` / `campaign_get`, or create it with the actual `brief` and
`objectives`. Check `plan_get`, then call `plan_run` after approval of its
200-credit new-run cost. Review `concept_list`, approve the selected concepts,
and use `creative_produce` after production approval. Keep the same
`campaign_id` throughout. Creating a campaign or linking a project does not run
the planner; verify the actual run before claiming campaign planning happened.
- **The user asks for a carousel or static post:** create with
`project_create { project_type: "image", title, aspect_ratio }`, then use
`project_ask` on the same project through planning and approved generation.
Keep one image-mode scene per slide, source/requested slide order, and on-slide
text. `export_render.image_urls` contains the rendered slides in order, with
text and the selected watermark setting applied; `output_url` is the PNG/ZIP.
Use a video project only when a video is explicitly requested.
- **The user asks for one complete original video or video clone:** use
`project_create` / `project_list`, then `project_ask`, Studio's content-planning
agent. Pass the full brief and assets. For planning only, use `generate:false`
and `media_credit_limit:0`; AI usage is still charged. After approval continue
on the **same project** with `generate:true` and the approved media estimate
allowance, poll the job, inspect the project and export. If the user selected
a campaign for organization, pass its `campaign_id` to `project_create`.
- **The user asks only for written briefs, scripts or prompts:** use
`draft_briefs` / `draft_clone`. `draft_briefs` always saves in the separate
“From your agent” draft container; it cannot target the user's selected
campaign, run its planner or supply concepts to `creative_produce`.
- **The user asks for an individual asset or manual editing:** use the model
catalog, quote and individual generation/timeline tools. Do not silently
replace a requested planning workflow with manual scene-by-scene generation.
If the user changes direction while work is running, inspect the existing jobs
and saved work. Reuse the selected campaign/project and successful clips; do not
create a second campaign just because standalone briefs are running. Explain any
additional planning cost before starting it. If tools are deferred, discover/load
`plan_run` or `project_ask`; if permissions prevent their use, explain the missing
permission rather than substituting another workflow.
## Deliver generated media
For a generation request, use `models_list` and `generation_estimate` to quote
the settings and cost. After the user approves, start the matching generation
tool or `project_ask { generate:true }`. Reuse approval for the agreed request
and budget; confirm changes that fall outside that authorization. Briefs and prompts
alone do not fulfill a request for a generated video.
Poll `jobs_get` until succeeded or failed. Share the generated file URL from
the successful result, such as `result.video.url` for `video_generate`.
For a project, inspect `project_get`, call `export_render`, and poll its job
for `result.ouPreview of the first 4,000 characters. Read full instructions →
