Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_poll_answer_voters

Read-only

Retrieve users who voted for a specific poll answer in a Discord channel message; supports pagination to inspect voter lists.

Instructions

List users who voted for a poll answer. [GET /channels/{channel_id}/polls/{message_id}/answers/{answer_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>",
      "message_id": "<message_id>",
      "answer_id": "<answer_id>"
    },
    "name": "list_poll_answer_voters"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoReturn items after this ID (pagination)
limitNoMax results
answer_idYesPoll answer ID (1-based)
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds the endpoint shape, which lightly signals REST pagination semantics, but says nothing about result ordering, whether votes from bots or deleted users appear, or how pagination terminates — genuine behavioral gaps the annotations do not fill.

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?

One short sentence plus a bracketed endpoint reference — front-loaded and free of filler. It is slightly redundant with the tool name itself, but the endpoint annotation earns its space by anchoring the tool to a known API surface.

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?

This is a simple read-only list tool with fully described schema and annotations covering safety, so the description is close to sufficient. However, with no output schema there is nothing anywhere telling the agent what a voter record looks like (user object IDs, pagination envelope), which is the main remaining gap for an enumeration endpoint.

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 all five parameters including after, limit, answer_id (1-based) and channel_id are already documented in the schema. The description adds no syntax, format, or interaction detail (e.g. how after interacts with limit), 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?

The description states a specific verb and resource — 'List users who voted for a poll answer' — and appends the REST path, so an agent knows exactly which entity is being enumerated (voters on a specific answer). It is clearly distinct from siblings such as vote_in_poll (casting a vote) or end_poll, though it never names an alternative explicitly and largely mirrors the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the resource scoping: call it when you need the voters behind one poll answer. There is no explicit when-to-use statement, no prerequisites (e.g. that the poll must exist / have votes), and no guidance on when to prefer a different enumeration tool, so an agent must infer the context.

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