Image to Video by RunComfy
Inceptions AI INC v1.0.2
Animate photos and products
From the developer
Declared capabilities
- Animate still images
- Animate product photos
- Describe camera and subject motion
Declared limitations
- A private local still cannot be fetched remotely and must not be silently uploaded.
- Unsupported exact 360-degree reconstruction, product preservation and seamless-loop guarantees.
- Motion prompting alone does not authorize paid video generation.
Not specified in the available declarations: pricing & account requirements.
Onboarding example
Help me animate a landscape photo with a slow camera push-in; explain which image link you need.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 18, 2026.
Description
From the marketplace listing
Image to Video by RunComfy animates existing photos and product images into short clips using compatible models from the RunComfy catalog, including available Seedance, Wan and Kling image-to-video models. What you can do: - Turn an image into a short clip with described subject movement. - Add a slow push-in, pan or another supported camera movement to a still scene. - Animate a product photo while identifying the appearance details to check. - Retrieve a finished clip or check the status of an existing generation. Connect a RunComfy account to generate videos. Generations use your RunComfy account balance. Duration, resolution, audio and reference options depend on the selected model and its current input schema. The starting image must be available through an accessible HTTPS link. If a chat attachment cannot be passed to the model, the plugin asks for a usable image link. Motion may change faces, product shape, labels or background details; inspect the actual clip before using it. A single image cannot establish accurate unseen sides of an object, and seamless loops or exact motion are not guaranteed.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 18, 2026. Last seen Nov 18, 2026.
Similar plugins
Finding similar plugins… Results will appear here automatically.
Browse plugins →Keywords
Files & skills
File archives
Skill instructions
animate-product-photo9.58 KB
--- name: animate-product-photo description: Create short product-motion clips from supplied product photos with RunComfy, including gentle push-ins or restrained scene motion. Use for requested product animation; does not guarantee exact SKU details, unseen geometry, true 360-degree views or seamless loops. --- # Animate a product photo Generate the requested clip from the user's actual product photo through this plugin's MCP tools. Respond in the user's language. This skill needs no CLI, other plugin skill or assumed uploader. Use only this plugin’s current host-provided tool definitions: actual names, descriptions, typed outer arguments and allowed model scope. If current definitions cannot be verified, report an unverified connection binding, not that RunComfy lacks the product capability. If verified definitions offer no compatible operation, explain the connection-specific limitation before spending. Do not assume a discovery tool, switch endpoints, invent operations or bypass the connection through workflow/deployment execution. ## Source product and motion brief Build a still-to-motion brief around the supplied product image: camera movement, any explicitly requested product movement, scene movement, ending goal and supported duration. Keep the product checklist attached to that clip. The deliverable is the requested animation and observed temporal/product drift, not a newly invented product scene or reconstructed hidden geometry. Identify the actual source reference and, where supplied, its intended SKU/variant, color, label/logo/text, silhouette, proportions, material and important parts. A generated or illustrative source is a visual reference, not proof that a physical product or genuine SKU exists. A SKU name alone is not evidence of an unseen product's appearance. Resolve conflicting product references instead of blending them or substituting a generic item. Use the requested camera move, scene motion, duration, aspect ratio and clip count. For a restrained product-stability brief, favor a motion description matching that request, such as a gentle push-in with the product stationary. Do not add a spin, lid opening, new label or physically different product action that the user did not request. Preservation is a goal to inspect, not a guarantee. Motion models can warp edges, change labels or color and invent unseen surfaces. Do not certify catalog accuracy, exact logo text, measured geometry or identity throughout every frame. A single photo does not provide a true 3D model: explain the limitation before a requested exact 360-degree product rotation, rather than promising a faithful view of hidden sides. Do not guarantee seamless loops or an exact first/last-frame match. ## Reachable file and exposed operation Confirm that the starting product reference is a still image. A product video or audio URL is not a valid substitute for the required image input. If the user supplied only a clip, request a still or use frame extraction only through an actually available, user-authorized feature; these MCP tools do not provide frame extraction. Any optional sound/reference input must be supported by the chosen model and cannot replace the starting product image. For reference media, use externally fetchable HTTPS URLs that an unauthenticated GET can retrieve. When the host supplies such a URL for the user’s attachment and access is authorized for this task, use it directly; do not request another upload. Local paths, `file://`, internal attachment/sandbox IDs and data URIs cannot be passed to the Model API. Without a usable URL, explain the limit and request a direct link or a genuinely available, authorized host upload. These MCP tools do not upload arbitrary media: do not invent hosting, publish private media without permission, embed account credentials in URLs or repurpose training uploads. 1. Select a currently exposed image-to-video operation and supported model that fit the supplied still and complete mot
Preview of the first 4,000 characters. Read full instructions →
animate-still9.21 KB
--- name: animate-still description: Animate a supplied still image into a short video with RunComfy, such as gentle subject motion or a camera move. Requires a remotely accessible image; does not guarantee exact identity, seamless loops or unsupported audio controls. --- # Animate a still image Use this plugin's RunComfy MCP tools to turn the user's actual still into the requested clip. Respond in the user's language. No CLI, cross-plugin skill or automatic uploader is assumed. Use only this plugin’s current host-provided tool definitions: actual names, descriptions, typed outer arguments and allowed model scope. If current definitions cannot be verified, report an unverified connection binding, not that RunComfy lacks the product capability. If verified definitions offer no compatible operation, explain the connection-specific limitation before spending. Do not assume a discovery tool, switch endpoints, invent operations or bypass the connection through workflow/deployment execution. ## Resolve the image and intended motion For each clip, start with the actual still and make a compact motion brief: starting composition, camera movement, subject movement, ending goal and supported duration. Keep optional end frames or other references supplemental to that starting image, using them only when requested and supported. Deliver the generated clip with an honest check of the requested motion and any visible drift. Use the supplied source image, desired motion/camera move, duration, framing and clip count. Distinguish a moving camera from a moving subject. Preserve the user's scene rather than inventing a different source. If they requested only a motion prompt or plan, provide that and stop before paid execution. Confirm that the required starting asset is a still image. A reachable video or audio URL does not satisfy that requirement and must not be passed into an image field. If only video/audio is supplied, request a still image or use frame extraction only through an actually available feature authorized by the user; these MCP tools do not provide frame extraction. Optional sound or other references cannot replace the required starting image and must be supported by the exposed operation’s typed schema. For reference media, use externally fetchable HTTPS URLs that an unauthenticated GET can retrieve. When the host supplies such a URL for the user’s attachment and access is authorized for this task, use it directly; do not request another upload. Local paths, `file://`, internal attachment/sandbox IDs and data URIs cannot be passed to the Model API. Without a usable URL, explain the limit and request a direct link or a genuinely available, authorized host upload. These MCP tools do not upload arbitrary media: do not invent hosting, publish private media without permission, embed account credentials in URLs or repurpose training uploads. Explain a meaningful limitation before spending when it affects the request: generated motion can change faces, anatomy, small text and scene details. An input still cannot guarantee what an unseen side looks like. Do not promise exact identity, a true 3D reconstruction or a frame-perfect seamless loop. A requested loop is an intended motion, not proof that the final and first frames match. ## Match an exposed still-image video operation 1. Select a currently exposed image-to-video operation and supported model that fit the supplied still and complete motion brief. Use `generate_video` when the current host exposes a compatible definition, following its actual arguments and allowed model scope. The legacy `generate_seedance_pro_fast_video` / `bytedance/seedance-1.0/pro-fast/image-to-video` route is only an option if currently exposed and suitable; it does not define the current model range or edit existing clips. 2. Inspect the matched operation and model schemas for the starting image, prompt, duration, resolution/framing, audio and any requested additional references or end frame. U
Preview of the first 4,000 characters. Read full instructions →
Release notes
Adds two focused image-to-video skills for still-image and product-photo animation, multilingual discovery terms, bounded generation batches, current MCP tool contracts and request-bound video recovery. Clarifies model-specific audio limits and faithful result delivery.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- RunComfy
- Keywords
- See keywords
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Animate still images
- Animate product photos
- Describe camera and subject motion
- Retrieve generated video clips
Package observed Nov 18, 2026.
Technical details
- First seen
- Nov 18, 2026 · 06:00 UTC
- Last seen
- Nov 18, 2026 · 06:00 UTC
- Collection status
- Collected
plugin_asdk_app_6aec34d3f948819190ebf893693e7936
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.