Skip to main content
Glama
Sign In
@aiwerk/mcp-server-elevenlabs

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_speech_engine

Creates a speech engine configuration for ElevenLabs agents, defining TTS, ASR, turn detection, and privacy settings.

Instructions

Create Speech Engine

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": {
      "speech_engine": "<speech_engine>"
    },
    "name": "create_speech_engine"
  }
}

Input Schema

NameRequiredDescriptionDefault
asrNo
ttsNo
vadNo
nameNoName of the speech engine
tagsNoTags for categorization
turnNo
privacyNo
languageNoLanguage for the speech engine
overridesNo
call_limitsNo
conversationNo
speech_engineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, which provides a basic safety profile. However, the description adds no behavioral context such as what gets created, whether the operation is reversible, 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At three words, it is not wasteful in length, but it is severely under-specified rather than concise. A helpful description would need more content to earn its place.

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

Completeness1/5

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

For a tool with 12 parameters, deep nested objects, no output schema, and sparse schema coverage, the description is completely inadequate. It gives an agent no meaningful context for correct 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% across 12 parameters, including many complex nested objects. The description provides zero parameter information and therefore fails to compensate for the significant documentation gap.

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

Purpose2/5

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

The description is a tautology: it merely restates the tool name/title as 'Create Speech Engine' and adds no specific scope, resource detail, or sibling differentiation. It does not distinguish itself from update_speech_engine, delete_speech_engine, or get_speech_engine.

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 when-to-use guidance, prerequisites, or alternatives are provided. The agent must infer from the name alone that this creates a speech engine rather than updating or retrieving one.

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

Deploy Server

Other Tools