Fotor

Submit First Last Frame Video Task

submit_first_last_frame_video_task

Destructive

Starts one Fotor video generation task from first and last frames. May consume existing Fotor credits. Returns a task ID without waiting for completion; use get_task to check its status once. This tool does not poll for completion. Repeating the request may create another task and consume additional credits. Do not automatically retry when the submission outcome is uncertain. This tool does not purchase credits or initiate a checkout flow.

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": {
      "model_id": "<model_id>",
      "prompt": "<prompt>",
      "start_image_url": "<start_image_url>",
      "end_image_url": "<end_image_url>"
    },
    "name": "submit_first_last_frame_video_task"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	Describe the desired content, style and changes.
`duration`	No	Video duration in seconds from list_models; 0 uses default_duration.
`model_id`	Yes	Model ID from list_models; inspect its supported mode and parameters first.
`resolution`	No	Native output resolution from list_models; auto uses the model default.	auto
`aspect_ratio`	No	Explicit output aspect ratio supported by the model, such as 16:9; auto is not accepted.	auto
`audio_enable`	No	Generate native video audio; requires native_audio support. Independent of reference audio.
`end_image_url`	Yes	Accessible HTTPS image URL for the last frame.
`start_image_url`	Yes	Accessible HTTPS image URL for the first frame.

Output Schema

Name	Required	Description	Default
`status`	No	Submission accepted; generation is not yet confirmed complete.	submitted
`task_id`	Yes	Fotor task ID for get_task.
`model_id`	Yes	Model ID used for this task.
`media_type`	Yes	Generated media category.
`credits_increment`	No	Reported task credit cost; not an additional charge on each query. Null if unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 29, 2026

addedInput schema / properties / aspect_ratio / description

Added value: +"Explicit output aspect ratio supported by the model, such as 16:9; auto is not accepted."

addedInput schema / properties / audio_enable / description

Added value: +"Generate native video audio; requires native_audio support. Independent of reference audio."

addedInput schema / properties / duration / description

Added value: +"Video duration in seconds from list_models; 0 uses default_duration."

addedInput schema / properties / end_image_url / description

Added value: +"Accessible HTTPS image URL for the last frame."

addedInput schema / properties / model_id / description

Added value: +"Model ID from list_models; inspect its supported mode and parameters first."

addedInput schema / properties / prompt / description

Added value: +"Describe the desired content, style and changes."

addedInput schema / properties / resolution / description

Added value: +"Native output resolution from list_models; auto uses the model default."

addedInput schema / properties / start_image_url / description

Added value: +"Accessible HTTPS image URL for the first frame."

addedOutput schema / properties / credits_increment / description

Added value: +"Reported task credit cost; not an additional charge on each query. Null if unavailable."

addedOutput schema / properties / media_type / description
```
Added value: +"Generated media category."
```
addedOutput schema / properties / model_id / description
```
Added value: +"Model ID used for this task."
```

addedOutput schema / properties / status / description

Added value: +"Submission accepted; generation is not yet confirmed complete."

addedOutput schema / properties / task_id / description
```
Added value: +"Fotor task ID for get_task."
```

First observedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, but the description adds real value on top: credit consumption, fire-and-forget task ID return, no polling, and the non-obvious duplicate-charge risk on retry. The no-checkout clarification further scopes side effects beyond what annotations alone declare.

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

Conciseness4/5

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

Front-loaded with the core action and cost warning, then a sequence of scoping constraints. Mild redundancy between "Returns a task ID without waiting for completion" and "This tool does not poll for completion," which restate the same async trait.

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

Completeness5/5

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

With an output schema covering the returned task ID and rich annotations for safety, the description fills the remaining gaps an agent needs: credit cost, async non-polling behavior, retry hazards, and the absence of a checkout flow. Nothing essential for correct invocation is missing.

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 all eight parameters are already documented with defaults and constraints (e.g., aspect_ratio rejecting "auto"). The description only implies the start/end image inputs via "first and last frames," adding no syntax or format detail beyond the schema; baseline 3 applies.

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

Purpose5/5

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

States a specific verb ("Starts") and resource ("Fotor video generation task") plus the distinguishing input scope: "from first and last frames." This immediately separates it from siblings like submit_first_frame_video_task and submit_text_to_video_task without opening a schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent to get_task for status and warns against auto-retry when the outcome is uncertain, plus clarifies it does not purchase credits or start checkout (pointing away from get_credits). It gives clear downstream context but never explicitly contrasts when to prefer first_frame vs first_last_frame generation.

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

All Fotor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?