Sora 2 MCP Server

create_fade_animation

Transform static images into fade animation videos by applying fade-in, fade-out, or combined effects to create smooth visual transitions.

Instructions

Create a fade-in animation video from a static image. The image will fade from black to full visibility.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_path": "<image_path>"
    },
    "name": "create_fade_animation"
  }
}

Input Schema

Name	Required	Description	Default
`image_path`	Yes	Path or URL to the input image
`duration`	No	Duration of the fade animation in seconds (default: 3)
`output_path`	No	Path where the video will be saved (default: fade_animation.mp4)	fade_animation.mp4
`fade_type`	No	Type of fade effect: 'in' (fade in), 'out' (fade out), 'in-out' (fade in then out)	in

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Feb 3, 2026

TDQS

B3.1/5.0

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 that the tool creates a video and describes the fade effect, but lacks critical behavioral details: it doesn't specify file format requirements, performance characteristics, error handling, or what happens if the output path already exists. For a creation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 two sentences that directly state the tool's function and effect. Every word earns its place—there's no redundancy or unnecessary elaboration. It's front-loaded with the core purpose and follows with a clear explanation of the animation behavior.

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

Completeness3/5

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

Given the tool's moderate complexity (4 parameters, creation operation) and lack of annotations/output schema, the description is minimally adequate. It explains what the tool does but doesn't cover behavioral aspects, error conditions, or output details. For a video creation tool, users would benefit from more context about supported formats, performance, and result verification.

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 100%, so the schema already documents all four parameters thoroughly. The description mentions 'fade-in' specifically, which aligns with the default 'fade_type' value but doesn't add meaningful semantic context beyond what's in the schema. It doesn't explain parameter interactions or provide usage examples, so it meets the baseline for high schema coverage.

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: 'Create a fade-in animation video from a static image.' It specifies the verb ('create'), resource ('fade-in animation video'), and source material ('static image'). However, it doesn't explicitly distinguish this from sibling tools like 'create_video' or 'merge_videos' beyond mentioning the fade effect.

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. It doesn't mention sibling tools like 'create_video' (which might handle other animation types) or 'merge_videos' (which could combine videos). There's no context about prerequisites, limitations, or appropriate scenarios for fade animations versus other video creation methods.

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

Deploy Server