Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_directory_entry

Update a Discord channel's directory entry by changing its description or primary category using channel and entity IDs.

Instructions

Modify Directory Entry. [PATCH /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": "modify_directory_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesEntity ID
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
descriptionNoDescription
primary_category_idNoprimary category id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds that this is a PATCH operation against a channel-scoped endpoint, but does not state permissions, partial-update semantics for omitted fields, side effects, or response behavior.

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?

Two short fragments, front-loaded with the operation and endpoint, with no filler. It is terse and efficient, though the bracketed endpoint is the only detail beyond the name.

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?

The schema covers all inputs and annotations cover safety hints, so the definition is minimally sufficient to call the tool. However, for a write operation with no output schema, it remains thin on what the modification does, how omitted fields are treated, and what a successful call returns.

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% and all four parameters are documented in the schema. The description only echoes the two path parameters in the endpoint, adding no syntax, constraints, or meaning beyond what the schema already provides, so the baseline 3 applies.

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?

States the specific verb 'Modify' and resource 'Directory Entry', plus the PATCH endpoint path, so the operation and target are identifiable. It does not explain which entry attributes are modifiable or distinguish this from other modify_* siblings beyond the resource name.

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?

Provides no guidance on when to use this instead of create_directory_entry, delete_directory_entry, get_directory_entry, or other modify tools. There are no prerequisites, exclusions, or alternative-selection criteria; the endpoint only implies required IDs.

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