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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_branch_route

Modify an ElevenLabs agent branch's name, archived state, or protection status using its agent ID and branch ID.

Instructions

Update Agent 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>",
      "branch_id": "<branch_id>"
    },
    "name": "update_branch_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
agent_idYesThe id of an agent. This is returned on agent creation.
branch_idYesUnique identifier for the branch.
is_archivedNo
protection_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false, but the description adds nothing. It does not disclose which updates are irreversible, how protection_status affects later operations, or that renewal of protection perms may be required. For a mutation tool this is thin.

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?

Three words that merely echo the tool name. It is not overlong, but it is under-specified rather than concise, so no sentence earns 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?

A mutation tool with 5 parameters (40% described), no output schema, and open-world/non-idempotent annotations demands far more than a restated title. Nothing in the description helps an agent call it 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 40%, so the description is expected to compensate, and it does not. The enum-valued protection_status (writer_perms_required vs admin_perms_required) and the is_archived/name semantics are undocumented in the schema and unexplained in the description.

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?

"Update Agent Branch" restates the name and title rather than describing the operation. It does not say what fields can be changed (name, is_archived, protection_status) or what an agent branch is in this system, and it has no differentiation against siblings like create_branch_route, get_branch_route, or rebase_branch_onto_main.

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

Usage Guidelines1/5

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

No when-to-use guidance whatsoever. Nothing tells the agent when to update a branch vs. rebase it, merge it, or read it, even though several sibling tools touch the same branch resource.

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