Buzzy

Submit a video generation task that consumes credits; retries can create and charge for another video. Returns a task_id and project_id immediately. The generated video is placed on the project canvas as a video node. If you already have a project_id from an earlier generate_image or generate_video call in this conversation, pass it so all assets stay in the same project. If omitted, a project is created automatically — reuse the returned project_id on later generate calls. Hosts should confirm the arguments with the user before calling. On Apps-capable hosts a widget shows progress and the result — do not repeat the video as markdown. A loaded skill must still poll get_task until TASK_STATE_SUCCEEDED or a failure state; the widget does not replace get_task. On other hosts poll get_task with the task_id until it succeeds, then present the resource URLs as text. When a later skill tool needs a canvas reference, poll get_task until TASK_STATE_SUCCEEDED and pass the returned node_id as nodeIds. Do not call create_canvas_node with the generated URL — that duplicates the canvas node. model, resolution, aspect_ratio and duration are all required: call list_model, pick a model whose output_modalities include "video", and copy those values verbatim from that entry's resolutions / aspect_ratios / durations. Do not invent values — unsupported combinations fail.

Look up an async generation task by task_id. Returns state, node_id (the canvas node created for this generation), and the generated resources once it succeeds. Pass node_id as nodeIds on later skill tools to wire reference edges. Do not call create_canvas_node for the same image or video — that would duplicate the canvas node. While state is TASK_STATE_PENDING or TASK_STATE_RUNNING the task is still working — call get_task again until TASK_STATE_SUCCEEDED or a failure state; do not stop and wait for the user. Video generation usually takes minutes. Do not resubmit the generation, that would bill twice.

List generation models with the resolutions, aspect ratios, durations and input limits each one supports. Call this before generate_image or generate_video whenever you will pass resolution, aspect_ratio, or duration; copy those values verbatim from the matching model's arrays. You may skip this call when generating with a known model id and omitting those fields. Known generate model ids are listed on generate_image and generate_video.

List Buzzy skills or load one skill's instructions. Call with no argument to see skill names and what each one produces. Call with a skill name when the user asks for a product ad, brand commercial, cinematic clip, 3D clip, or story. When the loaded skill names a bundled file, call load_workflow_bundle_file with that exact path. Follow the loaded skill and call the tool names it lists. generate_image and generate_video return a task_id; poll get_task for the result and node_id.

Load a bundled file from a skill previously returned by load_workflow (a reference, script, or asset listed in files). Pass the exact path from that files list, e.g. "skills/mcp/ugc-ads/reference/intent-questions.md". Do not guess relative names from SKILL.md; copy the path verbatim.

Join two or more existing video clips into one video, in the given order. Use it only when there are at least two clips. Set is_generate_bgm when the merged video should also include a soundtrack.

Open the product editor when making an ad from a product page, product image, or product description. Pass productLink only when the user gave a product page URL; omit it for an image or a written description. This tool does not save the product. Wait for the user's Confirmed Product Info message, then call display_product_info.

Create a new background music version for a merged video that does not yet have a soundtrack. Pass the merged video. When earlier music exists, pass it so the result is the next version; existing nodes remain available.

Create a draft for the current Buzzy video workflow step: a product brief, selling-point analysis, ad storyboard, video script, scene breakdown, or image/video prompt. Choose prompt_key from the declared options for that workflow step and pass its task-specific inputs in instruction. This operation consumes credits and may add text or media nodes to the project canvas; retries may repeat those effects. Returns prompt_key and template-specific items; some include generated content text.

Derive new character and background records from a storyline the user edited. Call it after the user changes the story markdown and before generating images from those records. Pass the edited markdown and the previous character, background, and story records.

Request a presigned PUT URL for a local file the agent can upload itself. Use this when the MCP client cannot render the upload_resource widget (Hermes, curl, a code-execution sandbox). Pass filename and content_length (bytes). Run the returned curl PUT, then call confirm_file_upload with the returned url. Do not use this for user-provided local image/video/audio on Apps UI-capable hosts — call upload_resource so the widget uploads in the browser. Supports batch via files[].

Open the Buzzy upload widget for a user-provided local image, video, or audio file. Use it when the user asks to import a local media file and the MCP client can render Apps UI. Do not ask the user to upload the file directly into chat; remote MCP tools cannot read those attachments. The widget is the upload surface: the user chooses files in the browser, the browser uploads them directly to storage, then sends the CDN url(s) back for generate_image / generate_video / create_canvas_node. If the user provided an HTTP or HTTPS URL, pass it as url to import the file into Buzzy storage. Hosts that cannot render the widget should call upload_file (PUT local bytes) or pass url.