Skip to main content
Glama
cloud-ru-tech

mcp-server-mattermost

pin_message

Idempotent

Pin a specific message to a channel's pinned posts section using its unique post ID.

Instructions

Pin a message in a channel.

Pinned messages appear in the channel's pinned posts section. Pinning an already pinned message has no additional effect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYes26-character post/message identifier (e.g., 'o5w8h47pdfbzjc4d8w7dhnhren')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique post identifier
typeYesPost type (empty for regular posts)
edit_atYesLast edit timestamp
messageYesPost content (supports Markdown)
root_idYesRoot post ID if in thread
user_idYesAuthor user identifier
file_idsYesAttached file IDs
hashtagsYesSpace-separated hashtags
create_atYesCreation timestamp in milliseconds
delete_atYesDeletion timestamp (0 if not deleted)
is_pinnedYesWhether post is pinned
update_atYesLast update timestamp in milliseconds
channel_idYesChannel where posted
original_idYesOriginal post ID if edited
pending_post_idYesClient-side pending ID
Behavior4/5

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

Annotations provide idempotentHint and destructiveHint; the description adds explicit confirmation that pinning an already pinned message has no effect, and explains where pinned messages appear (channel's pinned posts section).

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?

The description is very concise: one sentence for the main action followed by two short clarifying sentences. It is front-loaded and contains no unnecessary words.

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 simple tool with one parameter and annotations, the description covers the main behavior and idempotency. It lacks mention of permissions or prerequisites, but given the output schema exists, it is fairly complete.

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 clear description of the 'post_id' parameter. The tool description does not add further parameter semantics, but baseline is 3 because schema already handles it.

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?

The description clearly states 'Pin a message in a channel' with the specific verb 'pin' and resource 'message' in a channel. It adds context about pinned posts section but does not explicitly distinguish from the sibling tool 'unpin_message'.

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?

The description does not provide guidance on when to use this tool vs alternatives like 'unpin_message' or other channel operations. It only states the action and idempotency, but no when-to-use or when-not-to-use advice.

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