Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_directory_entries

Read-only

Lists directory entries for a Discord channel by channel ID, with optional type and category filters.

Instructions

List Directory Entries. [GET /channels/{channel_id}/directory-entries]

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": "list_directory_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoType
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 externally. The description adds nothing beyond the endpoint path — no pagination behavior, no result scoping, no mention of what channels are eligible despite channel_id being required.

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 very short and front-loaded with no filler, but the brevity comes from under-specification rather than discipline; the second sentence is a raw route rather than useful agent-facing context.

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 list operation with three parameters, no output schema, and several near-identical siblings, the description should say what is returned and how it relates to the partial/search variants. None of that is present, leaving the agent to guess.

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 are documented in the schema itself and the baseline is 3. The description adds no extra meaning about channel_id, type, or category_id, so it neither helps nor hurts.

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 text is essentially the tool name restated ("List Directory Entries") plus a raw HTTP route. It never explains what a directory entry is or how this differs from siblings such as list_partial_directory_entries or get_directory_entry, so the agent gets no discrimination signal.

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, when-not-to-use, or alternative-selection guidance. The agent cannot infer from this text whether to call this or the partial/search variants.

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