Skip to main content
Glama
cloud-ru-tech

mcp-server-mattermost

create_channel

Create a new public or private channel in a specified Mattermost team. The authenticated user is set as the channel admin.

Instructions

Create a new channel in a team.

Creates either a public (O) or private (P) channel. The authenticated user becomes the channel admin. Each call creates a new channel; use get_channel_by_name to check if it exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesChannel name (lowercase, no spaces)
headerNoChannel header
purposeNoChannel purpose
team_idYes26-character team identifier (e.g., 'o5w8h47pdfbzjc4d8w7dhnhren')
channel_typeNoChannel type: O=public, P=private, D=direct message, G=group messageO
display_nameYesHuman-readable channel name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique channel identifier
nameYesURL-friendly channel name
typeYesChannel type: O=public, P=private, D=direct, G=group
headerYesChannel header text
purposeYesChannel purpose description
team_idYesTeam this channel belongs to
create_atYesCreation timestamp in milliseconds
delete_atYesDeletion timestamp (0 if not deleted)
update_atYesLast update timestamp in milliseconds
creator_idYesUser ID who created the channel
display_nameYesHuman-readable channel name
last_post_atYesTimestamp of last post
total_msg_countYesTotal message count
Behavior4/5

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

The description adds behavioral context beyond the annotations: the authenticated user becomes admin, and each call creates a new channel (non-idempotent). It correctly notes O and P types, though the schema includes D and G. No contradiction with destructiveHint=false.

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 concise sentences, each adding value: purpose, channel types, admin and idempotency guidance. No filler.

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?

Given the tool's complexity (6 params, schema coverage 100%, output schema exists), the description covers key behaviors and provides a useful check-idempotency tip. Slightly incomplete by not mentioning output structure, but output schema handles that.

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%, so baseline is 3. The description adds contextual insight (admin, idempotency) but does not elaborate on specific parameters beyond the schema's descriptions.

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 verb 'Create' and the resource 'a new channel in a team'. It distinguishes from siblings by specifying channel types (public/private) and notes the user becomes admin, which differentiates from other channel creation tools like create_direct_channel.

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?

The description advises using get_channel_by_name to check existence, which guides against duplicates. However, it does not mention when not to use this tool (e.g., for direct channels) or prerequisites like team membership, leaving some gaps.

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/cloud-ru-tech/mcp-server-mattermost'

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