Skip to main content
Glama

delete_channel

DestructiveIdempotent

Removes a channel when allowDevDelete is enabled and moves its logs to the trash, where an admin can restore or empty them.

Instructions

Deletes a channel (off by default — works only when the user turns on allowDevDelete in the admin app settings). Logs move to the trash, where the admin app can restore or empty them.

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": {
      "channelId": "<channelId>"
    },
    "name": "delete_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYesChannel ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description earns credit for the extra layer: the feature-flag prerequisite and the fact that logs go to trash and remain restorable or emptyable by the admin app. That soft-delete behavior is exactly the kind of consequence the annotations cannot express, though it leaves unclear whether the channel container itself is permanently removed.

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, front-loaded with the destructive action and immediately followed by the availability caveat and recovery behavior. No filler or restatement of the tool name.

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 one-parameter destructive mutation with no output schema, the definition covers precondition, effect, and recoverability, which is nearly everything an agent needs. The only gap is guidance on sourcing the channelId and confirmation of whether channel metadata survives alongside the logs.

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 a single well-documented channelId parameter, so the schema already does the work and the baseline is 3. The description adds no meaning beyond it, such as where an agent should obtain a valid channel ID (e.g. list_channels).

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?

The description opens with a specific verb and resource, 'Deletes a channel', which distinguishes it from create_channel and from the sibling delete_server by resource scope. An agent can identify the operation without inspecting the schema.

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

Usage Guidelines4/5

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

It supplies a concrete gating precondition: the tool is off by default and only functions when allowDevDelete is enabled in admin settings, which warns the agent off calling it speculatively. It stops short of naming an alternative workflow, though the sibling list offers no other channel-deletion path.

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