Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_webhook_with_token

Read-only

Retrieve a Discord webhook's details using its webhook ID and token to inspect configuration or integrate webhook-based notifications.

Instructions

Get Webhook with Token. [GET /webhooks/{webhook_id}/{webhook_token}]

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

Input Schema

NameRequiredDescriptionDefault
webhook_idYesWebhook ID
webhook_tokenYesWebhook token

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. The description adds nothing beyond that — no note on token sensitivity, no statement about what is returned, no error behavior for invalid tokens. It is purely a name plus a route.

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 only two fragments long, so there is no wasted prose, but that brevity comes from under-specification rather than discipline. The route is front-loaded, which is mildly useful for an agent mapping to an API.

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?

This is a simple two-parameter read with annotations and no output schema, so the bar is modest, but the description still says nothing about what the call yields or when it fails. An agent has no basis to choose it over get_webhook without opening both schemas.

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% with two required string parameters, so the schema already carries parameter meaning. The endpoint template in the description corroborates that both IDs are path components, but adds no format or validation detail. Baseline 3 applies.

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 with Token" restates the tool name verbatim, and the only added information is the HTTP route [GET /webhooks/{webhook_id}/{webhook_token}]. It does not explain what a webhook-with-token lookup returns or how it differs from the sibling get_webhook, so an agent must infer its distinct purpose from the name alone.

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, no mention of the alternative get_webhook (which takes no token), and no note about prerequisites such as owning the token. The agent gets no routing signal beyond the name.

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