Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_create_webhook

Create a webhook on a Discord channel to send automated messages and integrate with external services.

Instructions

Create a webhook on a channel.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
channelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states 'Create a webhook', implying a write operation, but fails to mention required permissions (e.g., 'Manage Webhooks'), side effects, rate limits, or whether the webhook is created immediately or asynchronously.

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

Conciseness2/5

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

The description is extremely concise (one sentence), but it is underspecified and lacks necessary details. Conciseness should not come at the expense of completeness; additional context is needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations, output schema, and parameter descriptions, the single-sentence description is wholly insufficient. It does not explain return values (e.g., webhook ID), error handling, or preconditions, leaving the AI agent with little guidance for correct invocation.

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

Parameters1/5

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

Schema coverage is 0% and the description adds no information about the two required parameters (name, channelId). The description does not explain what each parameter does or provide any constraints (e.g., name length limits). This is a significant gap.

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 'Create a webhook on a channel' clearly states the action (create) and the resource (webhook) with location, distinguishing it from related sibling tools like discord_delete_webhook or discord_list_webhooks. However, it could be more specific about the type of webhook (e.g., Discord incoming webhook).

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?

No guidance is provided on when to use this tool versus alternatives (e.g., discord_execute_webhook or discord_edit_webhook). There is no mention of prerequisites, permissions, or when not to use it.

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