Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_channel_webhooks

Read-only

Retrieve all webhooks configured in a specific Discord channel by channel ID to review integrations, manage automation endpoints, and audit channel webhook usage.

Instructions

List Channel Webhooks. [GET /channels/{channel_id}/webhooks]

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>"
    },
    "name": "list_channel_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 fully covered elsewhere. The description contributes only the HTTP route '[GET /channels/{channel_id}/webhooks]', which merely restates that it is a read of channel-scoped webhooks and adds no behavioral detail such as pagination or return contents.

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?

Two compact fragments with the operation named first and the route second; nothing is padded or buried. It is perhaps too terse to earn a top score, but there is no wasted wording.

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?

For a one-parameter read tool with full schema coverage and annotations covering safety, the essentials are present. However, it never says whether results include inherited/guild-level webhooks or how the list is scoped, which is the main ambiguity an agent would face here.

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% and the single channel_id parameter is already documented as accepting text, voice, thread, forum, or DM channel IDs. The description adds no meaning beyond the schema, so the baseline of 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?

States a specific verb and resource ('List Channel Webhooks'), which is unambiguous about what is retrieved. The 'Channel' qualifier implicitly distinguishes it from list_guild_webhooks, though that distinction is never made explicit in the text.

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 tool versus list_guild_webhooks or list_channel_integrations, both of which sit in the same namespace. The agent must infer the channel-vs-guild scope from the name alone.

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