mcp-server-mattermost

list_bookmarks

Read-onlyIdempotent

List all saved links and files in a channel, returned in sort order. Use to view pinned resources without searching messages.

Instructions

List all bookmarks in a channel.

Returns bookmarks in sort order. Use to see saved links and files pinned to a channel. For searching messages, use search_messages instead.

Note: Requires Entry, Professional, Enterprise, or Enterprise Advanced edition (not available in Team Edition). Minimum version: v10.1.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel_id`	Yes	26-character channel identifier (e.g., 'o5w8h47pdfbzjc4d8w7dhnhren')
`bookmarks_since`	No	Timestamp to filter bookmarks updated since

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.1Sep 10, 2026

addedOutput schema / properties / result / items / properties / file

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "description": "Uploaded file metadata.\n\nNote: Go source uses CreatorId field name, but JSON response uses \"user_id\".\n\nSee: https://github.com/mattermost/mattermost/blob/master/server/public/model/file_info.go",
+      "properties": {
+        "channel_id": {
+          "description": "Channel where file was uploaded",
+          "type": "string"
+        },
+        "create_at": {
+          "description": "Upload timestamp in milliseconds",
+          "type": "integer"
+        },
+        "delete_at": {
+          "description": "Deletion timestamp",
+          "type": "integer"
+        },
+        "extension": {
+          "description": "File extension without dot",
+          "type": "string"
+        },
+        "has_preview_image": {
+          "default": false,
+          "description": "Has generated preview",
+          "type": "boolean"
+        },
+        "height": {
+          "default": 0,
+          "description": "Image height in pixels",
+          "type": "integer"
+        },
+        "id": {
+          "description": "Unique file identifier",
+          "type": "string"
+        },
+        "mime_type": {
+          "description": "MIME type",
+          "type": "string"
+        },
+        "name": {
+          "description": "File name",
+          "type": "string"
+        },
+        "post_id": {
+          "default": "",
+          "description": "Associated post ID",
+          "type": "string"
+        },
+        "size": {
+          "description": "File size in bytes",
+          "type": "integer"
+        },
+        "update_at": {
+          "description": "Last update timestamp",
+          "type": "integer"
+        },
+        "user_id": {
+          "description": "Uploader user identifier (CreatorId in Go)",
+          "type": "string"
+        },
+        "width": {
+          "default": 0,
+          "description": "Image width in pixels",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "id",
+        "user_id",
+        "channel_id",
+        "create_at",
+        "update_at",
+        "delete_at",
+        "name",
+        "extension",
+        "size",
+        "mime_type"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "File metadata for file bookmarks"
+}

removedOutput schema / properties / result / items / properties / file_info

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "File metadata for file bookmarks"
-}

First observedv0.5.1Jul 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavioral context beyond those annotations: it states the returned items are in sort order and calls out edition/version constraints (Entry, Professional, Enterprise, Enterprise Advanced; minimum v10.1).

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?

Four short sentences, each earning its place: purpose, output ordering, use case, and availability constraint. The essential information is front-loaded and there is no filler.

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?

For a read-only list tool with full schema coverage and an output schema, the description is complete. It includes the intended use, an explicit alternative, sorting behavior, and edition/version restrictions, so an agent has what it needs to select and invoke the tool correctly.

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%, so the schema fully documents both parameters. The description does not add detail about bookmarks_since or the channel_id format, but the schema already covers this, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'List all bookmarks in a channel.' This clearly identifies the operation and scope, and the sibling-differentiating note 'For searching messages, use search_messages instead' helps distinguish it from a nearby tool.

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?

The description explicitly states when to use the tool ('Use to see saved links and files pinned to a channel') and names an alternative for a different need ('For searching messages, use search_messages instead'). This gives the agent clear routing guidance.

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