infinitetalk-mcp

audio_to_video

Create a video from a source image and audio by submitting an InfiniteTalk task on RunAPI. Returns task ID, status, and output URLs.

Instructions

Create a InfiniteTalk task on RunAPI (audio to video). Returns a task id, status, and output URLs.

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": {
      "source_image_url": "<source_image_url>",
      "source_audio_url": "<source_audio_url>"
    },
    "name": "audio_to_video"
  }
}

Input Schema

Name	Required	Description
`seed`	No	Declared type: integer.
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	No	Declared type: string.
`timeout_ms`	No
`callback_url`	No	Declared type: string.
`poll_interval_ms`	No
`source_audio_url`	Yes	Declared type: string.
`source_image_url`	Yes	Declared type: string.
`output_resolution`	No	Declared type: string. Known values: "480p", "720p".

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.2.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- removedInput schema / properties / model / enum
```
Removed value: -[
-  "infinitetalk-from-audio"
-]
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string. Known values: \"480p\", \"720p\"."
```
- removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "480p",
-  "720p"
-]
```
- addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / prompt / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / seed / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / seed / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / source_audio_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / source_image_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
Changed6 schema fields changedv0.1.7Aug 5, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_audio_url / type
```
Added value: +"string"
```
- addedInput schema / properties / source_image_url / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[
+  "source_image_url",
+  "source_audio_url"
+]
```
First observedv0.1.0Jun 24, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the async task model and the return shape (task id, status, output URLs). It omits cost/credit implications (a check_pricing sibling exists), auth requirements (a login sibling exists), typical generation latency, and what happens when polling times out.

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?

Two short sentences, front-loaded with the action and target, and the second sentence delivers the only return-value information available since no output schema exists. No filler.

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?

For a 10-parameter asynchronous generation tool with no annotations and no output schema, the description leaves major gaps: authentication requirements, cost, the meaning of 'wait' versus callback_url, and the timeout/poll-interval behavior. The return-shape sentence is the only genuinely useful addition.

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 80%, but most entries are placeholder text like 'Declared type: string', so the schema conveys little semantic meaning. The description adds nothing about seed, prompt, model, callback_url, timeout_ms, or poll_interval_ms, so it neither compensates nor detracts; 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 ('Create') and resource ('InfiniteTalk task on RunAPI (audio to video)'), so an agent can tell it apart from the retrieval sibling get_task. It does not explicitly name competing tools, but the create-vs-fetch distinction is inferable from the verb.

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 on when to use this versus get_task or check_pricing, no mention of whether credentials/login are prerequisites, and no note that the built-in 'wait' polling may make a separate get_task call unnecessary. Usage is only implied by the tool name and inputs.

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

Deploy Server