Fotor

Submit Text To Video Task

submit_text_to_video_task

Destructive

Starts one Fotor text-to-video generation task. 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>"
    },
    "name": "submit_text_to_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	Output aspect ratio supported by the model; auto uses its default.	auto
`audio_enable`	No	Generate native video audio; requires native_audio support. Independent of reference audio.

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.

Changed11 schema fields changedOct 29, 2026

addedInput schema / properties / aspect_ratio / description

Added value: +"Output aspect ratio supported by the model; auto uses its default."

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 / 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."

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.6/5.0

Behavior5/5

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

The description adds substantial context beyond the annotations: credit consumption, asynchronous task-ID return, no polling, duplicate submission risk, retry caution, and the fact that it does not purchase credits. These details are fully consistent with the destructive, non-idempotent, non-read-only annotations.

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?

The description is front-loaded with the core action and keeps each sentence focused on operational safety or next steps. There is minor redundancy between "without waiting for completion" and "does not poll for completion," but the repetition reinforces an important behavioral constraint.

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?

For a destructive, non-idempotent submission tool with an output schema and annotations, the description covers everything an agent needs: credit cost, async behavior, status-check routing, retry caution, and scope boundaries. No critical return-format or safety detail 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 the parameter meanings are already well documented in the schema, including model_id, duration, resolution, and audio support. The description adds no parameter-specific guidance beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: "Starts one Fotor text-to-video generation task." It also distinguishes the immediate return behavior from the sibling get_task, so an agent can tell this is a submission tool rather than a status-check tool.

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

Usage Guidelines5/5

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

It gives explicit follow-up and caution guidance: use get_task to check status, do not poll, and do not automatically retry when the outcome is uncertain. It also names the credit-consuming duplicate-submission risk, which directly informs when to call or avoid calling it.

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?