Skip to main content
Glama
RamboRogers

FAL Image/Video MCP Server

by RamboRogers

vidu_image

Animate images into videos using motion prompts and duration controls. Convert static pictures to dynamic content with specified aspect ratios and guidance settings.

Instructions

Vidu I2V - High-quality image animation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_urlYesURL of the input image
promptYesMotion description prompt
durationNoVideo duration in seconds5
aspect_ratioNo16:9
negative_promptNoWhat to avoid in the video
cfg_scaleNoHow closely to follow the prompt

Implementation Reference

  • Handler function executing the 'vidu_image' tool logic. Dispatched for all image-to-video models. Calls FAL endpoint, processes video output with download/data URL handling.
    private async handleImageToVideo(args: any, model: any) {
      const { 
        image_url, 
        prompt, 
        duration = '5', 
        aspect_ratio = '16:9',
        negative_prompt,
        cfg_scale
      } = args;
    
      try {
        // Configure FAL client lazily with query config override
        configureFalClient(this.currentQueryConfig);
        const inputParams: any = { image_url, prompt };
        
        // Add optional parameters
        if (duration) inputParams.duration = duration;
        if (aspect_ratio) inputParams.aspect_ratio = aspect_ratio;
        if (negative_prompt) inputParams.negative_prompt = negative_prompt;
        if (cfg_scale !== undefined) inputParams.cfg_scale = cfg_scale;
    
        const result = await fal.subscribe(model.endpoint, { input: inputParams });
        const videoData = result.data as FalVideoResult;
        const videoProcessed = await downloadAndProcessVideo(videoData.video.url, model.id);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                model: model.name,
                id: model.id,
                endpoint: model.endpoint,
                input_image: image_url,
                prompt,
                video: {
                  url: videoData.video.url,
                  localPath: videoProcessed.localPath,
                  ...(videoProcessed.dataUrl && { dataUrl: videoProcessed.dataUrl }),
                  width: videoData.video.width,
                  height: videoData.video.height,
                },
                metadata: inputParams,
                download_path: DOWNLOAD_PATH,
                data_url_settings: {
                  enabled: ENABLE_DATA_URLS,
                  max_size_mb: Math.round(MAX_DATA_URL_SIZE / 1024 / 1024),
                },
                autoopen_settings: {
                  enabled: AUTOOPEN,
                  note: AUTOOPEN ? "Files automatically opened with default application" : "Auto-open disabled"
                },
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new Error(`${model.name} generation failed: ${error}`);
      }
    }
  • Input schema definition for image-to-video tools, including 'vidu_image', generated dynamically in generateToolSchema.
    } else if (category === 'imageToVideo') {
      baseSchema.inputSchema.properties = {
        image_url: { type: 'string', description: 'URL of the input image' },
        prompt: { type: 'string', description: 'Motion description prompt' },
        duration: { type: 'string', enum: ['5', '10'], default: '5', description: 'Video duration in seconds' },
        aspect_ratio: { type: 'string', enum: ['16:9', '9:16', '1:1'], default: '16:9' },
        negative_prompt: { type: 'string', description: 'What to avoid in the video' },
        cfg_scale: { type: 'number', default: 0.5, minimum: 0, maximum: 1, description: 'How closely to follow the prompt' }
      };
      baseSchema.inputSchema.required = ['image_url', 'prompt'];
    }
  • src/index.ts:119-127 (registration)
    MODEL_REGISTRY.imageToVideo array registering 'vidu_image' tool with its FAL endpoint and metadata. Used for tool listing, schema generation, and dispatch.
    imageToVideo: [
      { id: 'ltx_video', endpoint: 'fal-ai/ltx-video-13b-distilled/image-to-video', name: 'LTX Video', description: 'Fast and high-quality image-to-video conversion' },
      { id: 'kling_master_image', endpoint: 'fal-ai/kling-video/v2.1/master/image-to-video', name: 'Kling 2.1 Master I2V', description: 'Premium image-to-video conversion' },
      { id: 'pixverse_image', endpoint: 'fal-ai/pixverse/v4.5/image-to-video', name: 'Pixverse V4.5 I2V', description: 'Advanced image-to-video' },
      { id: 'wan_pro_image', endpoint: 'fal-ai/wan-pro/image-to-video', name: 'Wan Pro I2V', description: 'Professional image animation' },
      { id: 'hunyuan_image', endpoint: 'fal-ai/hunyuan-video-image-to-video', name: 'Hunyuan I2V', description: 'Open-source image-to-video' },
      { id: 'vidu_image', endpoint: 'fal-ai/vidu/image-to-video', name: 'Vidu I2V', description: 'High-quality image animation' },
      { id: 'luma_ray2_image', endpoint: 'fal-ai/luma-dream-machine/ray-2/image-to-video', name: 'Luma Ray 2 I2V', description: 'Latest Luma image-to-video' }
    ]
  • src/index.ts:480-481 (registration)
    Dispatch logic in CallToolRequestSchema handler that routes 'vidu_image' calls to the image-to-video handler based on model ID.
    } else if (MODEL_REGISTRY.imageToVideo.find(m => m.id === name)) {
      return await this.handleImageToVideo(args, model);
  • Helper function to download and process video output (local path, data URL, auto-open), called by the handler.
    async function downloadAndProcessVideo(videoUrl: string, modelName: string): Promise<any> {
      const filename = generateFilename('video', modelName);
      const localPath = await downloadFile(videoUrl, filename);
      const dataUrl = await urlToDataUrl(videoUrl);
      
      // Auto-open the downloaded video if available
      if (localPath) {
        await autoOpenFile(localPath);
      }
      
      const result: any = {};
      
      // Only include localPath if download was successful
      if (localPath) {
        result.localPath = localPath;
      }
      
      // Only include dataUrl if it was successfully generated
      if (dataUrl) {
        result.dataUrl = dataUrl;
      }
      
      return result;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'High-quality image animation' implies a generative/mutation operation, but it doesn't disclose critical behavioral traits: whether this is a synchronous or asynchronous operation, typical processing time, rate limits, authentication requirements, cost implications, or what happens if the image_url is invalid. For a generative tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with just 6 words: 'Vidu I2V - High-quality image animation'. It's front-loaded with the tool name and immediately states its core function. Every word earns its place, with no wasted verbiage or redundant information. The structure efficiently communicates the essential purpose in minimal space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a generative tool with 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns (video URL? status object?), doesn't mention any prerequisites or limitations, and provides no context about the 'Vidu I2V' technology or quality characteristics. For a complex image-to-video tool in a crowded space of alternatives, more contextual information would be valuable.

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 83% (high), so the baseline is 3 even without parameter information in the description. The description adds no specific parameter semantics beyond what's already in the schema descriptions (e.g., 'URL of the input image', 'Motion description prompt'). It doesn't explain relationships between parameters or provide usage examples that would add meaningful context beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Vidu I2V - High-quality image animation' clearly states the tool's purpose: animating images with high quality. It specifies the verb 'animation' and resource 'image', distinguishing it from text-based tools like vidu_text. However, it doesn't explicitly differentiate from other image animation siblings like luma_ray2_image or pixverse_image beyond the 'Vidu I2V' branding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools for image generation and animation (e.g., luma_ray2_image, pixverse_image, hunyuan_image), there's no indication of this tool's specific use cases, strengths, or limitations compared to others. The description only states what it does, not when it's appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RamboRogers/fal-image-video-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server