Skip to main content
Glama

Coline

Update channel

update_channel
Idempotent

Renames a channel or changes its description, topic, or whether it's private. Needs a channel owner or admin.

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": {
      "workspace": "<workspace>",
      "channel": "<channel>"
    },
    "name": "update_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
typeNo
topicNo
channelYesChannel id (from list_conversations or list_channels) or its slug.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNo

Output Schema

NameRequiredDescriptionDefault
idYes
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the privilege requirement, which is real value, but omits partial-update behavior (are unspecified fields left untouched?), what happens to mentions or links on rename, and how a null topic/description is treated. With rich annotations, a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the mutation scope front-loaded before the permission caveat. Nothing is restated redundantly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool, the definition covers what it changes, what it requires, and the field set; an output schema exists so return values need no explanation. The main residual gap is null-clearing semantics for topic and description, which an agent could get wrong.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, and the two documented parameters (channel, workspace) are already described in-schema. The description compensates well for the undocumented ones by naming the four mutable fields: name, description, topic, and type/private. It stops short of clarifying the nullable semantics of topic and description or the 280-character limits, so not a 5.

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 specific verb-plus-resource with the exact set of mutable fields: rename, description, topic, and private/public. An agent can immediately tell this is the settings-mutation tool for an existing channel, distinct from archive_channel or delete_channel, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The 'needs a channel owner or admin' clause tells the agent a permission prerequisite, which is useful pre-call guidance. However, it never says when to prefer this over siblings like set_channel_role or update_settings, and gives no exclusions or failure conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources