Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_threads

Read-only

Find and filter Discord threads within a channel by name, tag, archived state, and sort criteria, with limits and pagination for locating relevant conversations.

Instructions

Search Threads. [GET /channels/{channel_id}/threads/search]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel_id": "<channel_id>"
    },
    "name": "search_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNotag
nameNoName
slopNoslop
limitNoMax results
max_idNomax id (ID)
min_idNomin id (ID)
offsetNoSkip this many results
sort_byNoSort by
archivedNoArchived
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
sort_orderNoasc or desc
tag_settingNotag setting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description adds only the HTTP path; it says nothing about pagination semantics for limit/offset, how sorting behaves, or how archived threads are treated, which are the real behavioral questions for a 12-parameter search.

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

Conciseness3/5

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

It is only two fragments, so there is no wasted wording, but that is brevity through omission rather than disciplined conciseness. The endpoint token is the only substantive content and is not front-loaded into an explanation an agent can act on.

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

Completeness2/5

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

For a tool with 12 parameters, no output schema, and non-obvious filtering (tags, archive state, id bounds, sort), the description is far too thin to guide correct invocation. An agent cannot tell what a result looks like, how results are ordered by default, or what slop and tag_setting change.

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 every parameter is documented in the schema itself, and the baseline of 3 applies. The description contributes no additional meaning to ambiguous fields such as slop, tag_setting, or sort_by, but it is not required to given full schema coverage.

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

Purpose2/5

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

"Search Threads" is a near-verbatim restatement of the tool name, so it adds little beyond the identifier. The bracketed endpoint [GET /channels/{channel_id}/threads/search] does imply the search is scoped to a single channel, but the description never says so in words or distinguishes this from siblings like search_messages or list_guild_active_threads.

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 when-to-use guidance: nothing explains when to search threads versus listing active/archived threads or searching messages. No prerequisites, no exclusions, no mention of what happens when the query matches nothing.

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