Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_directory_entries

Read-only

Search directory entries in a Discord channel by query text, entry type, or category ID to find matching members or listings quickly.

Instructions

Search Directory Entries. [GET /channels/{channel_id}/directory-entries/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_directory_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoType
queryNoSearch text
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
category_idNocategory id

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, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description contributes nothing beyond the route: no result shape, ordering, pagination, or matching semantics ('query' exact vs fuzzy), which is exactly the context this tool needs.

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?

Two short fragments with no wasted words and the resource is front-loaded, but the brevity comes from under-specification rather than precision. The bare URL annotation reads like generated boilerplate rather than authored guidance.

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 search tool with four parameters, a required channel scope, and no output schema, the description omits anything about result contents or filtering behavior. Annotations cover the read-only safety profile, but nothing describes the search semantics an agent needs to call it 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 coverage is 100%, so all four parameters (type, query, channel_id, category_id) are documented in the schema and the 3 baseline applies. The description adds no meaning on top, e.g. how 'query' interacts with 'type' or 'category_id' filtering.

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?

The description restates the tool name ('Search Directory Entries') and appends a raw HTTP route. The endpoint reveals that the search is scoped to a channel, but the prose itself adds no verb-level detail about what is searched or what is returned, and it does not distinguish this from siblings such as list_directory_entries or search_app_directory.

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, no condition selecting it over the list_* directory siblings, and no mention of prerequisites or required permissions. The agent must infer everything from the name alone.

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