Skip to main content
Glama
cloud-ru-tech

mcp-server-mattermost

update_message

Edit a posted message by providing its ID and new content; supports rich attachments with colors and fields.

Instructions

Edit an existing message.

Can only edit your own messages (unless admin). The message will show as edited. Original content is replaced; edit history is not preserved.

Attachment examples:

  • Status alert: {"color": "danger", "title": "Build Failed", "text": "Tests failed on main"}

  • With fields: {"title": "Ticket", "fields": [{"title": "Status", "value": "Open", "short": true}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesNew message content
post_idYes26-character post/message identifier (e.g., 'o5w8h47pdfbzjc4d8w7dhnhren')
attachmentsNoRich message attachments with colors, fields, images

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?

Beyond the destructiveHint=false annotation, it explains that the message will show as edited, original content is replaced, and edit history is not preserved. This adds behavioral context.

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?

Very concise: one line for purpose, then bullet points for behavioral details and attachment examples. No wasted words, front-loaded.

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?

Covers all relevant aspects: editing, permissions, edit behavior, and rich attachment examples. The tool is simple and description is sufficient.

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 coverage is 100%, so baseline 3. The description includes attachment examples, which add significant meaning beyond the schema for that parameter.

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 starts with 'Edit an existing message', which is a clear verb+resource. It distinguishes from siblings like delete_message and post_message.

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?

It states 'Can only edit your own messages (unless admin)', providing clear context on when to use. It implies not to use if not own message and not admin. No explicit alternatives, but the condition is clear.

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