Skip to main content
Glama
RamboRogers

FAL Image/Video MCP Server

by RamboRogers

ltx_video

Convert images into animated videos by providing a motion description prompt. Specify duration, aspect ratio, and control parameters to generate videos from image inputs.

Instructions

LTX Video - Fast and high-quality image-to-video conversion

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 that executes the 'ltx_video' tool by calling the FAL.ai endpoint 'fal-ai/ltx-video-13b-distilled/image-to-video', processing input parameters, handling video output including downloads and data URLs.
    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 ltx_video, specifying required image_url and prompt, and optional parameters like duration, aspect_ratio, etc.
    } 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:120-120 (registration)
    Registration of the ltx_video tool in the MODEL_REGISTRY.imageToVideo array, defining its ID, endpoint, name, and description.
    { 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' },
  • src/index.ts:406-408 (registration)
    Dynamic registration of ltx_video tool schema during tools/list response by iterating over imageToVideo models.
    for (const model of MODEL_REGISTRY.imageToVideo) {
      tools.push(this.generateToolSchema(model, 'imageToVideo'));
    }
  • Dispatch logic in CallToolRequestSchema handler that routes 'ltx_video' calls to the handleImageToVideo function based on model ID.
    } else if (MODEL_REGISTRY.imageToVideo.find(m => m.id === name)) {
      return await this.handleImageToVideo(args, model);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'fast and high-quality' but doesn't cover critical aspects like rate limits, authentication needs, output format, or potential side effects (e.g., data processing or costs). This is inadequate for a tool with 6 parameters and no output schema.

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 a single, efficient sentence that front-loads the core functionality. It wastes no words and is appropriately sized for the tool's complexity, making it easy for an agent to parse quickly.

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 the tool's complexity (6 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits, output expectations, and usage context, which are crucial for an AI agent to invoke it correctly without structured support.

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 high at 83%, providing good documentation for parameters. The description adds no specific parameter details beyond the tool's general purpose, so it doesn't compensate for the 17% gap but doesn't detract either. Baseline 3 is appropriate given the schema does most of the work.

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 clearly states the tool's purpose as 'Fast and high-quality image-to-video conversion,' specifying the verb (conversion) and resource (image to video). However, it doesn't differentiate from sibling tools like 'luma_ray2_image' or 'pixverse_image' which might also involve video/image generation, leaving some ambiguity about uniqueness.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, ideal use cases, or comparisons to sibling tools, leaving the agent to infer usage based solely on the name and purpose.

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