Skip to main content
Glama
karbassi

slack-mcp

by karbassi

search_messages

Need to locate a Slack message? Search with text, channel, user, date filters and paginate results.

Instructions

Search for messages matching a query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch text. Supports Slack modifiers like ``in:#channel``, ``from:@user``, and ``before:2024-01-31``.
countNoResults per page (default 20, max 100).
cursorNoPagination cursor from ``response_metadata.next_cursor`` in a prior response (alternative to ``page``).
highlightNoWrap matched terms in highlight markers in the response.
pageNo1-based page number to return.
sortNoSort by ``score`` (relevance, default) or ``timestamp`` (recency).
sort_dirNoSort direction, ``asc`` or ``desc`` (default ``desc``).
team_idNoEncoded team ID to scope the search to (for org-wide tokens).
detailedNoReturn the full, uncompacted Slack response when True.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so description bears full burden. Only states 'Search for messages matching a query.' No disclosure of pagination, authentication, rate limits, or any behavioral traits beyond the minimal functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short (4 words) but fails to convey essential information. Lacks structure or front-loading of key points.

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

Completeness1/5

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

Despite having an output schema and 9 parameters with 0 annotations, the description provides no context about return values, usage scope, or how this tool fits into the broader search ecosystem.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states it searches messages, but is very generic. Sibling tools like search_modules_messages exist with similar purpose, and no differentiation is provided.

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?

No guidance on when to use this search vs alternatives like search_all or search_modules_messages. The description only says 'matching a query' without context.

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/karbassi/slack-mcp'

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