discord-mcp-server

create_menu

Create interactive dropdown menus in Discord channels for user selection. Specify options, channel, and menu ID to build custom selection interfaces.

Instructions

Crée un message avec un menu déroulant

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": {
      "channelId": "<channelId>",
      "customId": "<customId>",
      "options": "<options>"
    },
    "name": "create_menu"
  }
}

Input Schema

Name	Required	Description
`channelId`	Yes	ID du canal
`message`	No	Message à envoyer
`customId`	Yes	ID unique du menu
`placeholder`	No	Texte d'attente
`options`	Yes	Options du menu
`minValues`	No	Nombre minimum de sélections
`maxValues`	No	Nombre maximum de sélections

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 9, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'creates' implies a write operation, the description doesn't specify permissions required, rate limits, whether the menu is interactive, or what happens on invocation. It lacks critical behavioral details for a tool that likely modifies chat state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in French that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the return value, error conditions, or how the created menu behaves in context. Given the complexity and lack of structured data, more detail is needed to be complete.

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?

The description adds no parameter-specific information beyond what's in the schema, which has 100% coverage with detailed descriptions for all 7 parameters. The baseline is 3 since the schema does the heavy lifting, but the description doesn't enhance understanding of parameter interactions or usage examples.

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 tool 'creates a message with a dropdown menu', which provides a clear verb ('creates') and resource ('message with dropdown menu'). However, it doesn't differentiate from sibling tools like 'create_button' or 'create_interactive_quiz', leaving the specific use case ambiguous. The purpose is understandable but lacks sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context, or exclusions, and doesn't reference sibling tools like 'create_button' or 'create_poll' for comparison. Usage is implied but not explicitly defined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server