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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

patch_agent_settings_route

Modify an ElevenLabs agent's settings by updating only the specified fields. Provide the agent ID and the changes.

Instructions

Patches An Agent Settings

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>"
    },
    "name": "patch_agent_settings_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
tagsNo
agent_idYesThe id of an agent. This is returned on agent creation.
workflowNo
branch_idNoThe ID of the branch to use
proceduresNo
platform_settingsNo
conversation_configNo
version_descriptionNo
enable_versioning_if_not_enabledNoDeprecated: all agents are versioned. This parameter is ignored.

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 already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond this: it doesn't explain that PATCH semantics mean only supplied fields change, whether omitted fields are preserved, or what versioning side effects (version_description) imply.

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?

It is a single short phrase, but this is under-specification rather than conciseness. There is no front-loaded information beyond a restated name, so brevity buys nothing here.

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 10-parameter mutation tool with nested objects, no output schema, and low schema coverage, the description is completely inadequate. An agent cannot determine what is being patched, how partial updates behave, or what fields matter.

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?

With 10 parameters and only 30% schema description coverage, the description carries the burden of explaining parameters and contributes nothing. Fields like name, tags, workflow, procedures, platform_settings, and conversation_config are undocumented in both places, and the description does not compensate.

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 'Patches An Agent Settings' is essentially a title-case restatement of the tool name, adding no resource scope, no statement of what settings are affected, and no differentiation from siblings like update_tool_route or create_agent_route. It conveys only that a partial update happens to some agent-related settings.

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 indication of when to use this tool versus alternatives (e.g., update_settings_route, update_branch_route, or other agent mutation routes). No prerequisites, no exclusions, no context are provided.

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