Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

click_button

Clicks a button on a Discord bot message by label or custom ID, returning the bot's response or a modal to fill.

Instructions

Click a button on a bot message (by label or custom_id). Returns the bot's response or a modal to fill.

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": {
      "message": "<message>"
    },
    "name": "click_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoButton label (or emoji)
messageYesMessage link, or message ID with channel_id
custom_idNo
channel_idNo
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already disclose this is a non-read-only, open-world, non-destructive operation, so the safety profile is covered. The description adds genuinely useful outcome context ('Returns the bot's response or a modal to fill'), which tells the agent the call is state-changing and may require follow-up work. It does not explain what wait_seconds governs or whether a clicked button becomes unusable, leaving the interaction lifecycle partly opaque.

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?

Two sentences with zero filler; the identification method and the return behavior are both front-loaded so the agent can decide and call quickly.

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?

With no output schema, stating the possible return shapes (bot response vs. modal) is exactly the right move and is present. However, for a five-parameter mutating interaction tool, the undocumented wait_seconds and channel_id, plus the absence of any note on component expiry or permissions, leave the definition only adequate.

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 only 40%, so the description must compensate and largely does not. It echoes the label/custom_id choice that the schema already documents, while channel_id and, more importantly, wait_seconds are unexplained in both schema and description, leaving the caller guessing at the timing behavior.

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 pairs a concrete verb ('Click') with a specific resource ('a button on a bot message') and clarifies the two ways to identify the target: label or custom_id. The scope is unambiguous, though nothing distinguishes it from a hypothetical sibling for other interactive components such as select menus.

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 only implied: the agent can infer this is for interacting with bot messages' interactive components. There is no statement of when not to use it (for example, expired or already-acknowledged components), no mention of alternatives, and no prerequisites such as needing access to the message's channel.

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