Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_webhook

Read-only

Retrieves a Discord webhook by ID, letting you inspect its configuration before managing or using it.

Instructions

Get Webhook. [GET /webhooks/{webhook_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": {
      "webhook_id": "<webhook_id>"
    },
    "name": "get_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYesWebhook ID

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond the endpoint path: no auth requirements, no note on what happens with an invalid or deleted webhook ID, no indication of response shape or rate limiting.

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

Conciseness3/5

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

It is short and front-loaded with the action, with no redundant phrasing. However, brevity here comes from under-specification rather than discipline; the bracketed route is the only substantive content.

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 simple read tool with complete schema and annotations, the description could still note that it returns a webhook object, since no output schema exists. It also omits any differentiation from the token-based sibling, leaving the agent to guess which fetch variant to call.

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% for the single webhook_id parameter, so the schema already carries the semantics and a baseline of 3 applies. The description adds no format details (e.g., snowflake ID expectations), but nothing is missing that the schema does not cover.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get Webhook" restates the tool name and title rather than describing what is retrieved; the only added information is the HTTP route [GET /webhooks/{webhook_id}]. It gives no hint of what a returned webhook contains or how it differs from siblings like get_webhook_with_token.

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 when-to-use guidance and no mention of the closely related alternatives (get_webhook_with_token, modify_webhook, delete_webhook). An agent must infer from the name alone that this fetches a webhook by ID with standard authentication rather than token auth.

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