Skip to main content
Glama
runapi-ai

@runapi.ai/elevenlabs-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Why This Package?

@runapi.ai/elevenlabs-mcp is a focused Model Context Protocol server for the ElevenLabs model line on RunAPI. It gives MCP-compatible assistants direct access to 5 endpoints and 6 model variants without loading the full RunAPI catalog.

Use this per-model server when an agent should stay scoped to ElevenLabs. Use @runapi.ai/mcp when one assistant should discover every RunAPI model line.

Related MCP server: ElevenLabs MCP Server

Install

Add it to Claude Code:

claude mcp add elevenlabs -s user -- npx -y @runapi.ai/elevenlabs-mcp

Use project scope when the server should be shared with a repository:

claude mcp add elevenlabs -s project -- npx -y @runapi.ai/elevenlabs-mcp

Codex, Cursor, Windsurf, VS Code, Roo Code, and other MCP hosts can use the same stdio command:

{
  "mcpServers": {
    "elevenlabs": {
      "command": "npx",
      "args": ["-y", "@runapi.ai/elevenlabs-mcp"]
    }
  }
}

check_pricing works before sign-in. For task creation and status polling, ask your assistant to call the login tool. It opens a browser login and saves credentials to ~/.config/runapi/config.json, the same file used by runapi login. Headless and CI hosts can still set RUNAPI_API_KEY before starting the MCP host.

Ready-made examples are in examples/ for Claude, Cursor, Windsurf, VS Code, and Roo Code.

Tools

Tool

Auth

Purpose

isolate_audio

Yes

Create an ElevenLabs isolate audio task and optionally wait for a terminal status. Returns the task id, status, and output URLs.

speech_to_text

Yes

Create an ElevenLabs speech to text task and optionally wait for a terminal status. Returns the task id, status, and output URLs.

text_to_dialogue

Yes

Create an ElevenLabs text to dialogue task and optionally wait for a terminal status. Returns the task id, status, and output URLs.

text_to_sound

Yes

Create an ElevenLabs text to sound task and optionally wait for a terminal status. Returns the task id, status, and output URLs.

text_to_speech

Yes

Create an ElevenLabs text to speech task and optionally wait for a terminal status. Returns the task id, status, and output URLs.

get_task

Yes

Fetch the current status and latest payload for an existing task.

check_pricing

No

Look up current pricing for a ElevenLabs model and endpoint.

Models

ElevenLabs covers 6 model variants across 5 endpoints. Each tool accepts the models listed for it:

Tool

Models

isolate_audio

audio-isolation

speech_to_text

speech-to-text

text_to_dialogue

text-to-dialogue-v3

text_to_sound

sound-effect-v2

text_to_speech

text-to-speech-multilingual-v2, text-to-speech-turbo-v2.5

Model availability can change between releases. Use check_pricing or the ElevenLabs model page for the current catalog view.

Agent Prompts

Ask your assistant in natural language; it can inspect pricing, create the task, and return the task id plus output URLs.

Create a task

Run an ElevenLabs isolate audio task with RunAPI.

The assistant can call check_pricing, then isolate_audio, and return the task id, status, and output URLs.

Submit without waiting

Create the task but don't wait for it to finish.

The assistant calls the create tool with wait: false and returns the task id. Check on it later with get_task.

Check pricing before creating

Check current ElevenLabs pricing, then create the task if it matches my request.

The assistant calls check_pricing and can link to the ElevenLabs model page for the canonical catalog entry.

Configuration

The server resolves auth in this order:

  1. RUNAPI_API_KEY environment variable, useful for headless and CI hosts

  2. ~/.config/runapi/config.json, created by the MCP login tool or runapi login

  3. No key, which still allows check_pricing

The config file is normally managed by login. A pre-provisioned headless config can use:

{
  "apiKey": "your_runapi_key"
}

Do not commit real API keys.

Links

Resource

URL

ElevenLabs model page

https://runapi.ai/models/elevenlabs

npm package

@runapi.ai/elevenlabs-mcp

GitHub repository

runapi-ai/elevenlabs-mcp

RunAPI MCP overview

runapi.ai/mcp

RunAPI docs

runapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Available Tools

8 tools
check_pricingB

Look up RunAPI pricing for the elevenlabs model line.

ParametersJSON Schema
NameRequiredDescriptionDefault
modelNoModel slug. Defaults to the line's primary model.
actionNoEndpoint name. Defaults to the endpoint that offers the model.

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only states it's a lookup operation, failing to disclose any behavioral traits such as read-only nature, potential costs, or response format.

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 a single, concise sentence that front-loads the purpose. It contains no unnecessary words, though structure is minimal.

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 simple lookup tool with no output schema, the description omits behavioral details and return value information, leaving the agent under-informed for effective use.

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 baseline is 3. The description adds no extra parameter semantics beyond what the schema already provides.

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 clearly states the tool's purpose: 'Look up RunAPI pricing for the elevenlabs model line.' It uses a specific verb and resource, distinguishing it from sibling action tools like isolate_audio.

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 is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. Agents must infer usage from the description alone.

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

get_taskA

Fetch the current status and latest result payload for a elevenlabs task.

ParametersJSON Schema
NameRequiredDescriptionDefault
actionYesAsynchronous endpoint the task was created on.
task_idYesTask id returned when the task was created.

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'Fetch' indicates a read-only operation, which is transparent about its side effects. However, it does not disclose additional behavioral traits like rate limits, authentication needs, or what happens if the task is incomplete or invalid, leaving some gaps.

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?

The description is a single, front-loaded sentence with no redundancy. It communicates the core function efficiently, though it contains a minor grammatical error ('a elevenlabs'). Overall, it is concise and well-structured.

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?

Given the absence of annotations and output schema, the description is moderately complete but leaves questions about return format and error handling. It clearly states what is fetched, but does not explain the structure of the result payload or status values, which is important for an agent to interpret the response correctly.

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?

The schema description coverage is 100%, with both parameters (task_id and action) already documented. The description adds no extra parameter insights, so the baseline of 3 applies. It does not clarify relationships between parameters or provide usage examples.

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 uses a specific verb ('Fetch') and clearly identifies the resource ('current status and latest result payload for a ElevenLabs task'). It distinguishes itself from sibling action tools (isolate_audio, text_to_speech, etc.) which are async endpoints that create tasks, whereas this retrieves task status.

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

Usage Guidelines3/5

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

The description implies usage as a polling mechanism for tasks started on async endpoints, but it does not explicitly state when to use this tool versus alternatives. It lacks explicit guidance such as 'use this after initiating an async task' or mentions of when not to use it.

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

isolate_audioB

Create a ElevenLabs task on RunAPI (isolate audio). Returns a task id, status, and output URLs.

ParametersJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
timeout_msNo
callback_urlNo
poll_interval_msNo
source_audio_urlYes

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description is the sole source of behavioral disclosure. It states that the tool returns a task id, status, and output URLs, but omits critical behavioral traits such as asynchronous execution, polling behavior, or side effects. This leaves the agent unprepared for the task lifecycle.

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?

The description is one compact sentence that front-loads the key action and return value. It contains no fluff, making it immediately scannable, even though brevity sacrifices depth that other dimensions capture.

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?

The tool has six parameters, no output schema, and no annotations, yet the description fails to explain how parameters interact, what the output URLs contain, or how waiting/polling works. It is a minimal skeleton that leaves substantial gaps for an agent attempting to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (wait and model have descriptions), and the tool description adds no parameter explanations. Four parameters (timeout_ms, callback_url, poll_interval_ms, source_audio_url) remain semantically opaque despite being necessary for effective invocation.

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 specifies the action 'Create' on the resource 'a ElevenLabs task on RunAPI (isolate audio)', clearly differentiating it from siblings like text_to_speech or text_to_dialogue. The parenthetical 'isolate audio' removes any ambiguity about the task type.

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 guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or why isolate_audio would be preferred over sibling tools. The agent is left to infer situational appropriateness from the name alone.

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

loginA

Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

ParametersJSON Schema
NameRequiredDescriptionDefault
forceNoRe-run browser login when the current credential comes from the local config file.

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the interactive browser flow and the file write side effect (config.json). However, it does not mention that it may overwrite existing credentials or that it could block waiting for user input, though these are implied.

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?

The description is a single, well-structured sentence that front-loads the action ('Authenticate RunAPI') and provides necessary details without extraneous information.

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

Completeness4/5

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

For a simple login tool with one optional parameter and no output schema, the description covers the core purpose and side effect. It lacks an explicit statement that this is a prerequisite for other tools, but that is implied.

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% (the only parameter 'force' has a description). The tool description adds no additional meaning about parameters beyond the schema, so the baseline of 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?

The description clearly states the tool's purpose with a specific verb ('Authenticate'), target resource ('RunAPI'), method ('browser PKCE login flow'), and side effect (saving to config.json). It is distinct from sibling tools, none of which relate to authentication.

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

Usage Guidelines3/5

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

The description implies usage (to authenticate RunAPI) but does not explicitly say when to run it (e.g., before other RunAPI tools) or when to use the 'force' parameter. Since there are no alternative auth tools among siblings, 'vs alternatives' is not applicable.

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

speech_to_textB

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

ParametersJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
diarizeNo
timeout_msNo
callback_urlNo
language_codeNo
poll_interval_msNo
source_audio_urlYes
tag_audio_eventsNo

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 burden of behavioral disclosure. It usefully states that the tool returns a task id, status, and output URLs, implying an asynchronous task model. However, it does not mention the async nature explicitly, nor the wait/polling behavior, auth requirements, or cost implications.

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 concise, containing only two sentences, with the main point front-loaded. However, the grammar error 'a ElevenLabs' slightly detracts from polish, and it could arguably be more directly phrased as 'Transcribe audio using ElevenLabs via RunAPI.' Still, it is efficient and structurally clear.

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?

The tool has moderate complexity (9 parameters, async task creation) and no output schema, so the description must explain return values and behavioral nuances. It does mention the return format (task id, status, output URLs) but omits critical details like how to wait for completion, how callback_url works, what the language_code options are, and what diarize does. This makes the description incomplete for safe, correct use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no information about the parameters. The schema has 9 parameters but only one (model) has a description, leaving 78% undocumented. The description does not compensate by explaining source_audio_url, diarize, language_code, or the wait/timeout semantics, which is a significant gap for a tool with this many parameters.

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 clearly identifies the tool as creating an ElevenLabs speech-to-text task on RunAPI, which distinguishes it from sibling tools like text_to_speech and isolate_audio. The verb 'Create' and the resource 'task on RunAPI' are specific, and the parenthetical 'speech to text' confirms the function.

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

Usage Guidelines3/5

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

Usage is implied through the name and description—it is for creating speech-to-text tasks—but no explicit guidance is given about when to use this tool versus alternatives like get_task or text_to_speech. There are no exclusionary notes or alternative recommendations.

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

text_to_dialogueC

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

ParametersJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
dialogueYes
stabilityNo
timeout_msNo
callback_urlNo
language_codeNo
poll_interval_msNo

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. It does disclose that the tool creates a task and returns a task id, status, and output URLs, which implies an asynchronous workflow. However, it omits important behavioral details such as polling behavior, wait semantics, authentication requirements, or side effects.

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?

The description is two sentences, front-loaded with the core action and object, and contains no filler. Every word earns its place, making it highly concise and well-structured.

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?

Given the high complexity (8 parameters, async task creation) and no output schema or annotations, the description is too sparse. It does not cover parameter semantics, usage scenarios, or operational nuances, making it inadequate for reliable tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% and the description adds no parameter-level information. The 'dialogue' array, wait, stability, language_code, callback_url, timeout_ms, and poll_interval_ms are all unexplained, leaving the agent unable to construct a correct invocation based on the description alone.

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?

The description clearly states the action ('Create') and resource ('ElevenLabs task on RunAPI'), and clarifies the modality as text-to-dialogue. It distinguishes from speech_to_text but less clearly from sibling text_to_speech and text_to_sound, which is why it doesn't earn a 5.

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 guidance on when to use this tool versus alternatives like text_to_speech or text_to_sound. The description only states the tool's purpose without providing context or exclusions, so the agent receives no decision-making support beyond the tool's name.

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

text_to_soundC

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

ParametersJSON Schema
NameRequiredDescriptionDefault
loopNo
textYes
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
timeout_msNo
callback_urlNo
output_formatNo
duration_secondsNo
poll_interval_msNo
prompt_influenceNo

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for transparency. It discloses the return value (task ID, status, output URLs) and implies an asynchronous task creation, but it doesn't explain that the task may need polling (despite a 'wait' parameter in the schema), how authentication works, or potential side effects. The description is not misleading but is sparse.

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?

The description is two sentences, with the action verb front-loaded. It is concise and contains no unnecessary information, though it sacrifices detail for brevity.

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?

Given the moderate complexity (10 parameters, no output schema, no annotations), this description is insufficiently complete. It doesn't mention the asynchronous task model, the need for polling or using get_task, the sound-effect model, or parameter semantics. It provides only the core action and return format, which is not enough for an agent to invoke the tool correctly in varied contexts.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (wait and model). The description adds no parameter-level explanation beyond the name 'text to sound,' leaving the other 8 parameters undocumented in both the schema and description. This is a significant gap for a tool with 10 parameters.

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?

The description clearly states the tool creates an ElevenLabs text-to-sound task on RunAPI and returns a task ID, status, and output URLs. It uses a specific verb ('Create') and resource ('ElevenLabs task on RunAPI (text to sound)'), which distinguishes it from siblings like text_to_speech and text_to_dialogue, though it doesn't explicitly name alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives such as text_to_speech or text_to_dialogue. It simply states what the tool does without any context on appropriate use cases, exclusions, or prerequisites.

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

text_to_speechC

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

ParametersJSON Schema
NameRequiredDescriptionDefault
textYes
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
speedNo
styleNo
voiceNo
next_textNo
stabilityNo
timeout_msNo
timestampsNo
callback_urlNo
language_codeNo
previous_textNo
poll_interval_msNo
similarity_boostNo

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It mentions that the tool returns a task id, status, and output URLs, hinting at asynchronous behavior, but does not explain the task lifecycle, polling requirements, or any side effects. This is minimal and insufficient for a task-based tool.

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 a single concise sentence that gets to the point quickly. It is efficient, though the grammar is slightly awkward ('Create a ElevenLabs'). It earns a high score for brevity.

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?

Given the tool's complexity (15 parameters, async task, no output schema, no annotations, multiple siblings), the description is far from complete. It only provides a high-level overview and omits critical details about how to use the tool, what the required 'text' parameter does, and how to handle returned task IDs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% (2 of 15 parameters have descriptions). The description adds no parameter meaning, leaving the many parameters (e.g., voice, speed, style, stability) unexplained. It does not compensate for the low schema coverage.

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?

The description clearly states the action ('Create'), the resource ('ElevenLabs task on RunAPI'), and the domain ('text to speech'). It does not explicitly differentiate from sibling tools like text_to_dialogue or text_to_sound, but the core purpose is unambiguous.

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 is given on when to use this tool versus alternatives. The description does not mention contexts, exclusions, or prerequisites. It only states what the tool does, leaving the agent to infer usage.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 6 tool updatesv0.1.7
    • Changedget_task1 field changed
      • changedInput schema / properties / action / description
        Previous value: -"Endpoint the task was created on."New value: +"Asynchronous endpoint the task was created on."
    • Changedisolate_audio3 fields changed
      • addedInput schema / properties / callback_url
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / properties / source_audio_url / type
        Added value: +"string"
      • addedInput schema / required
        Added value: +[
+  "source_audio_url"
+]
    • Changedspeech_to_text6 fields changed
      • addedInput schema / properties / callback_url
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / properties / diarize
        Added value: +{
+  "type": "boolean"
+}
      • addedInput schema / properties / language_code
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / properties / source_audio_url / type
        Added value: +"string"
      • addedInput schema / properties / tag_audio_events
        Added value: +{
+  "type": "boolean"
+}
      • addedInput schema / required
        Added value: +[
+  "source_audio_url"
+]
    • Changedtext_to_dialogue5 fields changed
      • addedInput schema / properties / callback_url
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / properties / dialogue / items
        Added value: +{}
      • addedInput schema / properties / dialogue / type
        Added value: +"array"
      • addedInput schema / properties / language_code
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "dialogue"
+]
    • Changedtext_to_sound6 fields changed
      • 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"
+]
    • Changedtext_to_speech12 fields changed
      • addedInput schema / properties / callback_url
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / properties / language_code
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / properties / next_text
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / properties / previous_text
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / properties / similarity_boost
        Added value: +{
+  "type": "number"
+}
      • addedInput schema / properties / speed
        Added value: +{
+  "type": "number"
+}
      • addedInput schema / properties / stability
        Added value: +{
+  "type": "number"
+}
      • addedInput schema / properties / style
        Added value: +{
+  "type": "number"
+}
      • addedInput schema / properties / text / type
        Added value: +"string"
      • addedInput schema / properties / timestamps
        Added value: +{
+  "type": "boolean"
+}
      • addedInput schema / properties / voice
        Added value: +{
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "text"
+]
  2. 1 tool updatev0.1.6
    • Addedlogin
  3. 7 tool updatesv0.1.0
    • First observedcheck_pricing
    • First observedget_task
    • First observedisolate_audio
    • First observedspeech_to_text
    • First observedtext_to_dialogue
    • First observedtext_to_sound
    • First observedtext_to_speech
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: authentication, pricing, task status, and five different ElevenLabs task types (speech, sound, dialogue, transcription, source isolation). No overlap or ambiguity between tools.

Naming Consistency3/5

The tool names mix two patterns: verb_noun (get_task, login, isolate_audio, check_pricing) and noun_to_noun (speech_to_text, text_to_dialogue, text_to_sound, text_to_speech). While each group is internally consistent, the coexistence of two patterns reduces predictability.

Tool Count5/5

With 8 tools, the server is well-scoped for its purpose: covering authentication, pricing, status polling, and five core ElevenLabs task types. No redundant or unnecessary tools; the count fits the ideal range.

Completeness4/5

The set covers the main lifecycle: creating various task types, fetching status/results, authenticating, and checking pricing. Missing a cancel or list operation is a minor gap that agents can work around, but the core workflow is complete.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers