Skip to main content
Glama

Coline

Delete channel

delete_channel
DestructiveIdempotent

Deletes a channel and all its messages for everyone. This can't be undone; archive it to keep its history. 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": "delete_channel"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds what those hints cannot: the deletion is permanent, it removes all messages, it affects every member ('for everyone'), and it requires owner/admin rights. That is the extra context that changes an agent's decision to call.

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?

Three short clauses, each loaded: effect and scope first, irreversibility and alternative second, permission requirement third. No filler and the destructiveness is front-loaded.

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

Completeness5/5

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

For a destructive two-parameter tool this covers everything the agent needs: who may call it, what is destroyed, that it is irreversible, and the safer alternative. Return values are covered by the output schema, so their absence from the description is not a gap.

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 coverage is 100%, with both workspace and channel documented including where the ids come from (list_conversations, list_channels, workspaces.list). The description adds nothing about parameters, so the baseline 3 applies - the schema does all the work.

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

Purpose5/5

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

States a specific verb and resource plus the blast radius: 'Deletes a channel and all its messages for everyone.' The cascade scope separates it from softer siblings like archive_channel or leave_channel without needing to open any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not plus the alternative action ('archive it to keep its history') and a prerequisite gate ('Needs a channel owner or admin'). An agent has both a routing rule and a permission precondition before calling.

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