MCP Discord Bot Server

discord_search_messages

Find messages in a Discord channel by ID and query, returning matching message objects for review or retrieval.

Instructions

Search for messages in a Discord channel.

Args:
    channel_id: The ID of the channel to search in.
    query: The search query string.
    limit: Maximum number of results to return (default: 25).

Returns:
    JSON array of matching message objects.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return. Default is 25.
`query`	Yes	The search query string. Required.
`channel_id`	Yes	The ID of the Discord channel to search messages in. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only restates the arguments and the return type. It says nothing about Discord search limitations (e.g., guild-wide scope, permission requirements, rate limits, pagination, or ordering of results) that an agent would need to call this correctly.

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

Conciseness4/5

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

The description is short and front-loads the purpose before the argument list. The Args/Returns sections largely duplicate the schema and the output schema, which is mild waste but not bloat.

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?

With an output schema present, the description need not explain return values, and it correctly notes the JSON array return. However, for a search tool with no annotations, it omits scope, permission, and result-limitation context that materially affect correct invocation.

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 all three parameters (channel_id, query, limit) are already documented in the schema with the same wording the description repeats. The description adds no syntax, format, or constraint detail beyond that baseline.

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?

The description states a specific verb and resource ('Search for messages in a Discord channel'), which is clear and immediately actionable. It does not, however, distinguish this tool from the sibling discord_read_messages, so an agent must infer the difference from the names alone.

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?

There is no guidance on when to use search versus discord_read_messages, and no mention of prerequisites such as required Discord permissions for search. The only usage signal is the implicit 'query-based' framing of the word 'search'.

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

Deploy Server