Skip to main content
Glama

Unassign Bot from Channel

neuron_unassign_bot_from_channel

Remove a bot assignment from a WhatsApp channel by providing the unique channel ID.

Instructions

Remove the bot assignment from a WhatsApp channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the channel
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 burden. It only states the removal action but does not disclose side effects, permissions required, or reversibility. This is insufficient for an agent to understand the tool's full impact.

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?

A single sentence that is front-loaded and to the point. However, it could include more context without significant bloat, but it remains efficient.

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?

With no output schema and no annotations, the description is minimal. It does not address what the return value is, prerequisites, or how it differs from similar tools. The tool is simple, but the description lacks completeness for safe agent invocation.

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?

The input schema already provides full coverage (100%) for the single parameter 'id' with a description. The tool description adds no additional meaning beyond what the schema offers, so baseline 3 is appropriate.

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 clearly states the action ('Remove') and the resource ('bot assignment from a WhatsApp channel'). It is specific and distinguishable from siblings like 'neuron_assign_bot_to_channel'.

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 guidance on when to use this tool versus alternatives like 'neuron_remove_bot_channel' or 'neuron_assign_bot_to_channel'. The description does not include context for when it is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conquext/neuron-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server