Skip to main content
Glama

discord_send_embed

Send rich embed messages to Discord channels with customizable titles, descriptions, colors, images, and structured fields for clear information display.

Instructions

Send a rich embed message with title, description, color, fields, footer, image, thumbnail, author, URL, and timestamp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
titleNo
urlNoURL that makes the title clickable.
descriptionNo
colorNoHex color e.g. #5865F2
fieldsNo
authorNoAuthor block shown at the top of the embed.
thumbnail_urlNoSmall image shown in the top-right corner.
footerNo
image_urlNo
timestampNoIf true, adds the current timestamp to the embed.

Implementation Reference

  • The handler implementation for the discord_send_embed tool.
    case "discord_send_embed": {
      const channel = await getTextChannel(args.channel_id as string);
      const embed = buildEmbed(args);
      const sent = await channel.send({ embeds: [embed] });
      return { content: [{ type: "text", text: `✅ Embed sent (id: ${sent.id}) in #${channel.name}.` }] };
    }
  • The input schema for the discord_send_embed tool.
      name: "discord_send_embed",
      description: "Send a rich embed message with title, description, color, fields, footer, image, thumbnail, author, URL, and timestamp.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          title: { type: "string" },
          url: { type: "string", description: "URL that makes the title clickable." },
          description: { type: "string" },
          color: { type: "string", description: "Hex color e.g. #5865F2" },
          fields: {
            type: "array",
            items: {
              type: "object",
              properties: {
                name: { type: "string" },
                value: { type: "string" },
                inline: { type: "boolean" },
              },
              required: ["name", "value"],
            },
          },
          author: {
            type: "object",
            description: "Author block shown at the top of the embed.",
            properties: {
              name: { type: "string" },
              icon_url: { type: "string" },
              url: { type: "string" },
            },
            required: ["name"],
          },
          thumbnail_url: { type: "string", description: "Small image shown in the top-right corner." },
          footer: { type: "string" },
          image_url: { type: "string" },
          timestamp: { type: "boolean", description: "If true, adds the current timestamp to the embed." },
        },
        required: ["channel_id"],
      },
    },
  • Helper function used by discord_send_embed to construct the embed object.
    function buildEmbed(args: Record<string, unknown>): EmbedBuilder {
      const embed = new EmbedBuilder();
      if (args.title) embed.setTitle(args.title as string);
      if (args.url) embed.setURL(args.url as string);
      if (args.description) embed.setDescription(args.description as string);
      if (args.color) embed.setColor(args.color as ColorResolvable);
      if (args.footer) embed.setFooter({ text: args.footer as string });
      if (args.image_url) embed.setImage(args.image_url as string);
      if (args.thumbnail_url) embed.setThumbnail(args.thumbnail_url as string);
      if (args.timestamp) embed.setTimestamp();
      if (args.author) {
        const a = args.author as { name: string; icon_url?: string; url?: string };
        embed.setAuthor({ name: a.name, iconURL: a.icon_url, url: a.url });
      }
      if (args.fields) {
        const fields = args.fields as { name: string; value: string; inline?: boolean }[];
        embed.addFields(fields.map((f) => ({ name: f.name, value: f.value, inline: f.inline ?? false })));
      }
      return embed;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the action 'Send' but doesn't clarify if this is a write operation, what permissions are required, rate limits, or error handling. It also doesn't describe the return value or side effects, which is critical for a tool with potential mutations in Discord.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the key action and enumerates all embed components without redundancy. Every word serves to inform, making it appropriately sized and well-structured for quick comprehension.

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?

Given the tool's complexity (11 parameters, nested objects, no output schema, and no annotations), the description is incomplete. It doesn't address behavioral aspects like permissions, rate limits, or error responses, nor does it provide enough parameter guidance to compensate for the low schema coverage. For a Discord API tool with potential side effects, this leaves significant gaps.

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 45%, meaning many parameters lack descriptions in the schema. The description lists parameter names (e.g., title, description, color) but doesn't add meaningful semantics beyond what's implied by the names or schema. It partially compensates by highlighting the embed's components, but doesn't explain usage details like format constraints or interactions between 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?

The description clearly states the action ('Send a rich embed message') and lists the components included (title, description, color, fields, etc.), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'discord_send_message' or 'discord_send_multiple_embeds', which would require mentioning it's for single embeds with rich formatting.

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?

The description provides no guidance on when to use this tool versus alternatives like 'discord_send_message' (for plain text) or 'discord_send_multiple_embeds' (for multiple embeds). It also lacks context such as prerequisites (e.g., needing channel access) or exclusions, leaving the agent to infer usage from the tool name alone.

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/PaSympa/discord-mcp'

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