@runapi.ai/elevenlabs-mcp

text_to_sound

Convert text into sound effects or audio by creating an ElevenLabs task on RunAPI, returning a task ID, status, and output URLs.

Instructions

Create a ElevenLabs task on RunAPI (text to sound). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema

Name	Required	Description
`loop`	No	Declared type: boolean.
`text`	Yes	Declared type: string.
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`timeout_ms`	No
`callback_url`	No	Declared type: string.
`output_format`	No	Declared type: string. Known values: "mp3_22050_32", "mp3_44100_32", "mp3_44100_64", "mp3_44100_96", "mp3_44100_128", "mp3_44100_192", "pcm_8000", "pcm_16000", "pcm_22050", "pcm_24000", "pcm_44100", "pcm_48000", "ulaw_8000", "alaw_8000", "opus_48000_32", "opus_48000_64", "opus_48000_96", "opus_48000_128", "opus_48000_192".
`duration_seconds`	Yes	Declared type: number.
`poll_interval_ms`	No
`prompt_influence`	No	Declared type: number.

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."
```
addedInput schema / properties / duration_seconds / description
```
Added value: +"Declared type: number."
```
addedInput schema / properties / loop / description
```
Added value: +"Declared type: boolean."
```
removedInput schema / properties / model / enum
```
Removed value: -[
-  "sound-effect-v2"
-]
```

addedInput schema / properties / output_format / description

Added value: +"Declared type: string. Known values: \"mp3_22050_32\", \"mp3_44100_32\", \"mp3_44100_64\", \"mp3_44100_96\", \"mp3_44100_128\", \"mp3_44100_192\", \"pcm_8000\", \"pcm_16000\", \"pcm_22050\", \"pcm_24000\", \"pcm_44100\", \"pcm_48000\", \"ulaw_8000\", \"alaw_8000\", \"opus_48000_32\", \"opus_48000_64\", \"opus_48000_96\", \"opus_48000_128\", \"opus_48000_192\"."

removedInput schema / properties / output_format / enum

Removed value: -[
-  "mp3_22050_32",
-  "mp3_44100_32",
-  "mp3_44100_64",
-  "mp3_44100_96",
-  "mp3_44100_128",
-  "mp3_44100_192",
-  "pcm_8000",
-  "pcm_16000",
-  "pcm_22050",
-  "pcm_24000",
-  "pcm_44100",
-  "pcm_48000",
-  "ulaw_8000",
-  "alaw_8000",
-  "opus_48000_32",
-  "opus_48000_64",
-  "opus_48000_96",
-  "opus_48000_128",
-  "opus_48000_192"
-]

addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / prompt_influence / description
```
Added value: +"Declared type: number."
```
addedInput schema / properties / text / description
```
Added value: +"Declared type: string."
```
addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```

changedInput schema / required

Previous value: -[
-  "text"
-]New value: +[
+  "text",
+  "duration_seconds"
+]

Changed6 schema fields changedv0.1.7Aug 5, 2026
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / duration_seconds
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / loop
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / prompt_influence
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / text / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[
+  "text"
+]
```
First observedv0.1.0Jun 23, 2026

TDQS

C2.9/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 that this is an asynchronous task submission returning a task id, status, and output URLs, plus the implicit polling behavior of the 'wait' parameter. It says nothing about authentication, rate limits, cost, or what state a task is in when 'wait' is false (the get_task sibling is never referenced).

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?

Two tight sentences with the action front-loaded and the return shape following. Every sentence carries information, though the second sentence overlaps with what a reader would infer from the task-based naming.

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?

For a 10-parameter mutation tool with no annotations and no output schema, the description does useful work by stating the return values. It remains incomplete on how the many optional parameters interact, whether the call blocks by default, and how this differs from text_to_speech or when to fall back to get_task.

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%, so the schema already documents most parameters (including the 'wait' polling semantics and enum values for output_format). The description adds no parameter-level detail beyond what the schema provides, which is the expected baseline of 3.

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

Purpose3/5

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

The description gives a specific verb and resource ('Create a ElevenLabs task on RunAPI (text to sound)'), so the core action is clear. However, it does not distinguish this tool from the near-identical sibling 'text_to_speech', and the parenthetical 'text to sound' only deepens the ambiguity rather than resolving it.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative. With siblings like text_to_speech, text_to_dialogue, and get_task in the same namespace, the agent is left to guess which one to call.

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

Deploy Server

text_to_sound

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools