Skip to main content
Glama
Sign In
toffguy77

mattermost-mcp

by toffguy77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Channel Posts

get_channel_posts
Read-onlyIdempotent

Retrieve recent Mattermost channel posts newest first, with limits and since/before filters for paging through history or narrowing by time.

Instructions

Get recent posts from a Mattermost channel, newest first.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of posts to return. Default: 30.
sinceNoISO 8601 datetime — only return posts created after this timestamp.
beforeNoA post ID — return posts older than it, to page back through history.
channel_idYesThe channel ID (use list_channels or get_channel to find it).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / properties / before
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "A post ID — return posts older than it, to page back through history."
+}
    • changedInput schema / properties / channel_id / description
      Previous value: -"The channel ID (use list_channels to find it)."New value: +"The channel ID (use list_channels or get_channel to find it)."
  2. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered elsewhere. The description adds the sort order (newest first), which is genuinely useful for an agent consuming the results, but says nothing about pagination depth, rate limits, or what happens when the channel is empty.

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?

One sentence, front-loaded with the verb and resource, with the ordering constraint appended. Nothing is wasted and nothing needs trimming.

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 no explanation, and the input schema is fully documented. The only residual gap is that the description does not allude to paging back through history via the 'before' parameter, which is the tool's main non-obvious affordance.

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 description coverage is 100%, and the schema already documents limit, since, before, and channel_id in detail, including pagination semantics. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('Get recent posts from a Mattermost channel') plus the ordering ('newest first'), which implicitly separates it from get_thread, get_pinned_posts, and search_posts in the sibling list. It stops short of naming those alternatives explicitly, so it is clear but not fully differentiated.

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 word 'recent' hints at the intended use case, but there is no explicit guidance on when to reach for this versus search_posts, get_pinned_posts, or get_thread, and no stated exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools