teamspeak3-mcp

channel_update

Modify TeamSpeak 3 channel properties by channel ID: name, description, password, max clients, codec quality, and talk power presets.

Instructions

Update channel properties. Talk power presets: 0=normal, 50=moderated, 999=silent

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": {
      "channel_id": "<channel_id>"
    },
    "name": "channel_update"
  }
}

Input Schema

Name	Required	Description
`name`	No	New channel name
`password`	No	New channel password (empty string to remove)
`permanent`	No	Make channel permanent
`channel_id`	Yes	Channel ID to update
`talk_power`	No	Required talk power (0=normal, 50=moderated, 999=silent)
`description`	No	New channel description
`max_clients`	No	Maximum number of clients
`codec_quality`	No	Audio codec quality 1-10

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says 'update' but not whether this requires elevated permissions, whether changes are immediate/reversible, or what happens to unspecified properties. Only the talk_power preset meaning is conveyed.

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?

Two short sentences, front-loaded with the core action. However, the second sentence duplicates the schema's talk_power description, so it does not fully earn its place.

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?

For an 8-parameter mutation tool with no annotations and no output schema, the description is sparse: no permission requirements, no side-effect or return-value context, and no guidance on optional-vs-required fields beyond the schema's required list.

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?

Schema description coverage is 100%, so all 8 parameters are already documented, which sets the baseline at 3. The description restates the talk_power presets verbatim from the schema, adding no semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource ('Update channel properties'), which is enough to know it mutates a channel. It does not distinguish itself from sibling mutation tools such as channel_perm or cgroup_perm, which also modify channel-related state.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives (channel_create, channel_delete, channel_info, channel_perm). The agent must infer that this is the tool for modifying existing channel attributes.

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