Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_directory_entry

Creates a directory entry in a Discord channel for a specified entity, with optional type, description, and primary category assignment.

Instructions

Create Directory Entry. [POST /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": "create_directory_entry"
  }
}

Input Schema

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

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 readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. Yet the description adds nothing about permissions, required channel context, whether the entity must already exist, or what creation actually does. For a mutation tool with only generic annotations, this leaves important behavioral context undisclosed.

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?

The description is short and front-loaded, with no wasted wording. But it is terse to the point of being under-specified rather than genuinely concise, since the only content is a restated title and endpoint.

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 five-parameter mutation tool with no output schema and only generic annotations, the description should explain what the operation creates, likely permissions, and the role of fields like type and primary_category_id. None of that is present, leaving clear gaps for an agent to fill by inference.

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 80%, so the input schema already documents most parameters, and the description does not add any meaning beyond it. With high schema coverage, the baseline of 3 is appropriate even though the description contributes no parameter guidance.

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 gives a verb-plus-resource phrase ('Create Directory Entry') and an HTTP endpoint, so an agent can tell it creates a directory entry rather than reading or deleting one. However, it does not explain what a 'directory entry' is in this API's domain or how it differs from sibling creation tools such as create_application. The endpoint path adds little beyond the 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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives like modify_directory_entry or get_directory_entry. The description offers no conditions that would help an agent choose this tool over any other create-style sibling.

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