Skip to main content
Glama
ubie-oss

Slack MCP Server

by ubie-oss

slack_search_messages

Find Slack messages by keywords, user, date range, or channel using targeted search filters.

Instructions

Search for messages with specific criteria/filters. Use this when: 1) You need to find messages from a specific user, 2) You need messages from a specific date range, 3) You need to search by keywords, 4) You want to filter by channel. This tool is optimized for targeted searches. For general channel browsing without filters, use slack_get_channel_history instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoBasic search query text only. Use this tool when you need to: search by keywords, filter by user/date/channel, find specific messages with criteria. For general channel browsing without filters, use slack_get_channel_history instead. Do NOT include modifiers like "from:", "in:", etc. - use the dedicated fields instead.
in_channelNoSearch within a specific channel. Must be a Slack channel ID (e.g., "C1234567"). Use slack_list_channels to find channel IDs first.
from_userNoSearch for messages from a specific user. IMPORTANT: You cannot use display names or usernames directly. First use slack_get_users to find the user by name and get their user ID (e.g., "U1234567"), then use that ID here.
beforeNoSearch for messages before this date (YYYY-MM-DD)
afterNoSearch for messages after this date (YYYY-MM-DD)
onNoSearch for messages on this specific date (YYYY-MM-DD)
duringNoSearch for messages during a specific time period (e.g., "July", "2023", "last week")
highlightNoEnable highlighting of search results
sortNoSearch result sort method (score or timestamp)score
sort_dirNoSort direction (ascending or descending)desc
countNoNumber of results per page (max 100)
pageNoPage number of results (max 100)
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool is 'optimized for targeted searches' and advises against using modifiers in the query, but does not disclose behavioral traits such as pagination behavior, result limits beyond parameters, error handling, or rate limits. This is adequate but leaves gaps.

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 four well-structured sentences: first states the purpose, then lists four use cases, then explains optimization, and finally states the alternative. No superfluous content; front-loaded with key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, usage guidelines, and differentiation, but lacks information about return values or output format (no output schema). It also does not mention required permissions or error conditions. For a tool with 12 parameters, the description is moderately complete but could be more comprehensive.

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%, so the baseline is 3. The tool description adds little beyond what the schema descriptions already provide; it reiterates the high-level categories (keywords, user, date, channel) but does not offer additional parameter-specific insights that are not already in the schema field descriptions.

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 clearly states the tool searches for messages with specific criteria/filters, lists concrete use cases (by user, date, keywords, channel), and explicitly distinguishes it from sibling tool slack_get_channel_history for general browsing without filters.

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 provides explicit conditions for using the tool (four numbered scenarios) and directly advises when not to use it, directing to slack_get_channel_history instead. The schema descriptions reinforce this 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/ubie-oss/slack-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server