Fotor

Submit Soundtrack Task

submit_soundtrack_task

Destructive

Starts one Fotor soundtrack task from an image or video. Returns independent MP3 music. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "submit_soundtrack_task"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	No	Describe the desired music.
`model_id`	No	Soundtrack model ID from list_models.	mureka-auto
`image_url`	No	Accessible HTTPS image URL (jpg, jpeg, png or webp). Provide exactly one of image_url or video_url.
`video_url`	No	Accessible HTTPS video URL (mp4, mov, avi, mkv or webm). Provide exactly one of image_url or video_url.
`audio_end_ms`	No	Soundtrack end in integer milliseconds.
`audio_start_ms`	No	Soundtrack start in integer milliseconds. With audio_end_ms, use an interval of at least 3000 ms.

Output Schema

Name	Required	Description	Default
`error`	No	Stable failure code; null when no failure is reported.
`status`	Yes	Observed task state. processing does not distinguish queued or running; unknown is an unrecognized upstream state.
`task_id`	Yes	Fotor task ID for get_task.
`model_id`	Yes	Model ID used for this task.
`task_type`	Yes	Audio operation performed.
`media_type`	No	Generated media category.	audio
`result_url`	No	Completed output URL; availability is not guaranteed permanently. Audio output may be MP3 or ZIP.
`is_terminal`	Yes	Whether the task has completed, failed, timed out or been cancelled.
`result_format`	No	Completed file format: mp3 audio or zip archive; null until completed.
`failure_reason`	No	Safe failure summary; may be generic rather than the upstream root cause.
`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.

AddedOct 29, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare destructive/openWorld/non-idempotent, and the description goes beyond them: it discloses credit consumption, that repeats create duplicate tasks and cost more credits, that it returns immediately without polling, and that it does not purchase credits. That is exactly the operational context annotations alone cannot convey.

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 purpose and output, then the async/credit caveats. Slightly redundant: 'Returns a task ID without waiting for completion' and 'This tool does not poll for completion' say the same thing twice.

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?

Output schema covers return values, annotations cover safety, and the description fills the remaining gaps an agent needs: cost, async semantics, duplicate-task risk, no-retry advice, and the fact that it will not trigger a checkout. Nothing material 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%, including the image_url/video_url either-or constraint and the 3000 ms interval rule, so the description need not repeat parameter detail. It only adds a general 'image or video' framing, which the schema already covers, so baseline 3 applies.

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?

States a specific verb and resource ('Starts one Fotor soundtrack task from an image or video') and adds the output nature ('independent MP3 music'), so an agent knows exactly what is produced. It stops short of naming which sibling (e.g. submit_audio_track_task) to prefer for non-soundtrack audio, so differentiation is implied rather than explicit.

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 status checking to get_task and tells the agent not to poll here, and adds a no-auto-retry rule for uncertain outcomes. It does not state when to choose this over submit_audio_track_task or submit_song_edit_task, so full alternative routing is missing.

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?