Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_poll

Post a poll in a Discord channel or DM with a question and 2–10 answers, optionally enabling multiselect and setting a duration.

Instructions

Post a poll in a channel or DM.

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": {
      "question": "<question>",
      "answers": "<answers>"
    },
    "name": "create_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYes2-10 answers; prefix with an emoji + space to add one, e.g. "🍕 Pizza"
contentNo
user_idNoOr: a user ID to DM (opens the DM for you)
questionYes
channel_idNoChannel/thread/DM ID or a discord.com/channels/… link
multiselectNo
duration_hoursNo1-768 hours (default 24)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 known. The description adds only the channel/DM placement, and says nothing about permissions required, whether the poll is immediately visible, or what happens if duration or answer limits are exceeded.

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?

A single short, front-loaded sentence with no wasted words. Its brevity is a structural strength, though the terseness is penalized under other dimensions rather than this one.

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 7-parameter mutating tool with 57% schema coverage and no output schema, one sentence is far too thin. An agent gets no help on answer formatting limits, duration bounds, or how DM targeting interacts with channel targeting.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 57%, so several parameters (question, content, multiselect, and the required-call shape) are undocumented anywhere. The description contributes no meaning about answers, multiselect, duration, or the channel_id vs user_id choice, leaving it below the coverage baseline.

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?

"Post a poll" states a specific verb and resource, and "in a channel or DM" adds the target scope. Sibling names like vote_in_poll and end_poll are implicitly differentiated by the verb, but the description never explicitly contrasts them.

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 guidance on when to use this versus voting or ending a poll, and no stated prerequisites such as needing channel access or an existing DM. Usage is only inferred from the verb 'Post'.

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