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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

public_create_order

Creates an order that spends ElevenLabs credits. Use sandbox mode to generate an auto-progressing order without producer intervention.

Instructions

Create Order Spends ElevenLabs credits.

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": "public_create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
sandboxNoWhen true, creates a sandbox order that auto-progresses without producer intervention.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds one genuinely new trait — that the call spends ElevenLabs credits — which is useful cost context, but nothing about reversibility, permissions, or what an order becomes after creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Two short sentences with no padding, which is appropriately sized for a one-parameter tool. However the second sentence is grammatically broken ('Create Order Spends ElevenLabs credits'), which slightly impedes parsing.

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 zero-required-parameter tool with a fully described optional parameter and no output schema, the bar is low and the annotation set covers safety. What remains missing is the tool's place in the order lifecycle relative to its numerous order siblings, which is the main unresolved gap.

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?

There is a single optional parameter and schema coverage is 100%, so the sandbox flag is fully documented in the schema. The description adds no meaning about what a sandbox order is beyond what the schema already says, so baseline 3 applies.

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 verb+resource 'Create Order' is stated plainly, so the basic purpose is recoverable. But it is not distinguished from sibling order tools such as public_submit_order, public_upsert_order_item, or public_create/update variants, so an agent cannot tell which order-creation path to pick.

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 statement of when to use this tool, what prerequisites exist, or which alternative order endpoints exist. The only contextual hint is the credit-cost note, which is a consequence rather than guidance.

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