Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_directory_entry

Destructive

Removes a directory entry from a Discord channel using the provided channel and entity IDs.

Instructions

Delete Directory Entry. [DELETE /channels/{channel_id}/directory-entry/{entity_id}]

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>",
      "entity_id": "<entity_id>"
    },
    "name": "delete_directory_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesEntity ID
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is carried by structured data. The description adds only the raw endpoint path, disclosing nothing about whether deletion is permanent, what permissions are required, or what happens to associated entities — the kind of context a destructive operation warrants.

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 short and front-loaded, but the first sentence merely repeats the tool name and the second is a raw route string. Little is wasted, yet little is gained; brevity here is under-specification rather than disciplined concision.

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 destructive, open-world delete operation with no output schema, the description should explain the effect of deletion, permission requirements, and irreversibility. The annotations cover the danger flag, but the description leaves the agent without the operational context needed to call this safely.

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 both parameters (channel_id, entity_id) are already documented in the schema. The path template in the description only confirms they are path parameters, adding minimal meaning beyond the structured definition.

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?

The description states the verb and resource ('Delete Directory Entry'), which is specific enough to identify the operation, but it is essentially the tool name restated plus an HTTP route. It gives no sense of what a 'directory entry' is here or how this differs from sibling delete tools such as delete_channel or delete_guild.

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 or when-not-to-use guidance, no mention of alternatives (e.g. modify_directory_entry for edits), and no prerequisites or warnings. The agent must infer all selection logic 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