ElevenLabs

elevenlabs_public_create_order

Create Order. Creates a new Productions order in the workspace. The order starts in the open state and can be configured with items before submission.

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

Input Schema

Name	Required	Description	Default
`body`	No
`account`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The description adds useful behavioral context beyond annotations by stating the order starts open and remains configurable before submission. It does not explain permissions, return payloads, or side effects, but nothing contradicts the provided safety hints.

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 short and front-loaded, with the key information in the first substantive sentence. The opening phrase 'Create Order' is redundant with the tool name, but the rest of the text is efficient and contains no unnecessary 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?

The description captures the order lifecycle but omits essential details for safe invocation: what the account parameter means, what sandbox does, what the response contains, and how this connects to subsequent configuration/submission operations. Since there is no output schema and no parameter documentation, this is a meaningful gap.

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 does not explain either parameter, and schema description coverage is 0%. The meanings of account and body.sandbox are left entirely to the agent to infer from bare property names, which is insufficient for a tool that accepts optional structured options.

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 action: creating a new Productions order in the workspace. It distinguishes this tool from related siblings by specifying lifecycle details—begins in an open state and can be configured before submission—rather than covering update or submit operations.

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

Usage Guidelines4/5

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

The description provides clear context on when this tool is appropriate: it is the initial creation step, before order configuration and eventual submission. It does not explicitly name alternate tools such as update/submit, but the lifecycle language makes the intended usage understandable.

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

All ElevenLabs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.