@aiwerk/mcp-server-elevenlabs

create_branch_route

Create a new agent branch from a selected parent version, specifying its name, description, and optional workflow, conversation, or platform settings.

Instructions

Create A New Branch

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": {
      "agent_id": "<agent_id>",
      "parent_version_id": "<parent_version_id>",
      "name": "<name>",
      "description": "<description>"
    },
    "name": "create_branch_route"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name of the branch. It is unique within the agent.
`agent_id`	Yes	The id of an agent. This is returned on agent creation.
`workflow`	No
`description`	Yes	Description for the branch
`include_draft`	No	When true, the new branch uses the caller's draft procedure set instead of the branch tip. Requires parent_version_id to be the branch tip.
`parent_version_id`	Yes	ID of the version to branch from
`platform_settings`	No
`conversation_config`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already declare destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds no behavioral context whatsoever — nothing about branch creation semantics, whether the parent version must be the branch tip, or what include_draft implied constraints exist, even though the schema hints these constraints matter.

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?

The description is a single four-word sentence, which is brief but not concise in the useful sense — it omits everything an agent would need and contains no information beyond the tool name. It is under-specification rather than economy.

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 an eight-parameter mutation tool with no output schema and several non-trivial fields (parent_version_id tip constraint, include_draft, workflow definition), a bare title-like sentence is wholly inadequate. Nothing about the creation flow, constraints, or return value is conveyed.

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 63%, and the description supplies zero parameter information. Eight parameters include non-obvious ones like include_draft and platform_settings whose semantics the agent must glean purely from the schema; the description does nothing to compensate for the coverage gap.

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?

"Create A New Branch" states a specific verb and resource, so the basic operation is identifiable. However, it offers no differentiation from siblings such as get_branch_route, update_branch_route, merge_branch_into_target, or rebase_branch_onto_main, leaving the agent to infer from the name alone which branch operation is intended.

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, what prerequisites exist (agent_id, parent_version_id), or how it relates to the merge/rebase branch siblings. The agent gets no context for selecting it over alternatives.

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

Deploy Server