Skip to main content
Glama
cloud-ru-tech

mcp-server-mattermost

get_channel_by_name

Read-onlyIdempotent

Retrieve a Mattermost channel's metadata, including purpose, header, and member count, using its name and team ID.

Instructions

Get a channel by its name within a team.

Returns channel metadata including name, purpose, header, and member count. Use when you know the channel name but not the ID. For lookup by ID, use get_channel instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idYes26-character team identifier (e.g., 'o5w8h47pdfbzjc4d8w7dhnhren')
channel_nameYesChannel name (lowercase, no spaces)

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?

Annotations already declare readOnlyHint and idempotentHint. Description adds return field context (name, purpose, header, member count) consistent with read-only behavior.

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, front-loaded with purpose, no redundancy. Every sentence earns its place.

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?

Given simplicity, annotations, and output schema, description provides sufficient context for selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters with descriptions. Description adds value by hinting at return fields, though schema already details parameters.

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?

Description clearly states the tool gets a channel by name, returns metadata, and distinguishes from get_channel by ID lookup. Specific verb-resource pair.

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?

Explicitly states when to use (know name, not ID) and when not (use get_channel for ID lookup), providing clear guidance.

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