Skip to main content
Glama
EncryptMan

Discord MCP

execute_webhook

Send a message to a Discord channel via webhook, with optional embeds for rich formatting.

Instructions

Send a message via webhook, with optional embeds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
embedsNo
contentNo
usernameNo
webhook_idYes
webhook_tokenYes
Behavior2/5

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

No annotations provided; description only mentions basic behavior without details on idempotency, error handling, or rate limits, leaving significant gaps.

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?

Very short single sentence, but it is clear and front-loaded. However, it could be expanded to include more context without becoming verbose.

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?

With 5 parameters, no output schema, and no annotations, the description is far too brief to be complete. Missing critical details like authentication (webhook credentials) and parameter constraints.

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 coverage is 0%, and the description only mentions embeds, not explaining the required webhook_id/webhook_token or optional content/username parameters.

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?

Clearly states the action (send a message) and resource (via webhook) with optional embeds. Distinguishes from sibling tools like send_message, create_webhook, and delete_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 on when to use this tool over alternatives (e.g., send_message) or prerequisites like having webhook credentials.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EncryptMan/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server