Skip to main content
Glama

Coline

Add to channel

add_channel_members
Idempotent

Adds teammates (or the workspace's agents) to a channel. 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>",
      "userIds": "<userIds>"
    },
    "name": "add_channel_members"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
addedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact, the owner/admin authorization requirement, but says nothing about partial failures (e.g. users already in the channel), batching, or rate limits.

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 short sentences with zero waste, front-loading the action and following with the constraint. Nothing is repeated from the title or schema.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile for this idempotent, non-destructive write. The permission prerequisite is supplied; only edge-case behavior (already-a-member handling, the 50-user cap's implications) is left implicit, which is a minor gap for a tool this simple.

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% and each parameter already names its source (list_conversations/list_channels, find_people/list_members, workspaces.list), so the schema does the heavy lifting and the baseline is 3. The description does add one meaningful clarification the schema lacks: userIds may refer to the workspace's agents, not only people.

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 and resource: "Adds teammates (or the workspace's agents) to a channel." It is clear what the tool does and what it acts on, but it never names the inverse operation (remove_channel_member) or the related add_team_member, so an agent gets no explicit sibling differentiation from the description alone.

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 second sentence gives a real prerequisite (channel owner or admin), which is useful context for when the call will succeed. However, it gives no guidance on choosing this over remove_channel_member or add_team_member, and no exclusions or failure conditions beyond the permission note.

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