Skip to main content
Glama

send_channel_message

Send messages to Microsoft Teams channels with text, markdown formatting, mentions, attachments, and importance levels for team communication.

Instructions

Send a message to a specific channel in a Microsoft Team. Supports text and markdown formatting, mentions, and importance levels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdYesTeam ID
channelIdYesChannel ID
messageYesMessage content
importanceNoMessage importance
formatNoMessage format (text or markdown)
mentionsNoArray of @mentions to include in the message
imageUrlNoURL of an image to attach to the message
imageDataNoBase64 encoded image data to attach
imageContentTypeNoMIME type of the image (e.g., 'image/jpeg', 'image/png')
imageFileNameNoName for the attached image file

Implementation Reference

  • The main handler function that executes the tool: processes input (text/markdown, mentions, images), uses Microsoft Graph API to post the message to the channel, handles errors and returns success/error response.
    async ({
      teamId,
      channelId,
      message,
      importance = "normal",
      format = "text",
      mentions,
      imageUrl,
      imageData,
      imageContentType,
      imageFileName,
    }) => {
      try {
        const client = await graphService.getClient();
    
        // Process message content based on format
        let content: string;
        let contentType: "text" | "html";
    
        if (format === "markdown") {
          content = await markdownToHtml(message);
          contentType = "html";
        } else {
          content = message;
          contentType = "text";
        }
    
        // Process @mentions if provided
        const mentionMappings: Array<{ mention: string; userId: string; displayName: string }> = [];
        if (mentions && mentions.length > 0) {
          // Convert provided mentions to mappings with display names
          for (const mention of mentions) {
            try {
              // Get user info to get display name
              const userResponse = await client
                .api(`/users/${mention.userId}`)
                .select("displayName")
                .get();
              mentionMappings.push({
                mention: mention.mention,
                userId: mention.userId,
                displayName: userResponse.displayName || mention.mention,
              });
            } catch (_error) {
              console.warn(
                `Could not resolve user ${mention.userId}, using mention text as display name`
              );
              mentionMappings.push({
                mention: mention.mention,
                userId: mention.userId,
                displayName: mention.mention,
              });
            }
          }
        }
    
        // Process mentions in HTML content
        let finalMentions: Array<{
          id: number;
          mentionText: string;
          mentioned: { user: { id: string } };
        }> = [];
        if (mentionMappings.length > 0) {
          const result = processMentionsInHtml(content, mentionMappings);
          content = result.content;
          finalMentions = result.mentions;
    
          // Ensure we're using HTML content type when mentions are present
          contentType = "html";
        }
    
        // Handle image attachment
        const attachments: ImageAttachment[] = [];
        if (imageUrl || imageData) {
          let imageInfo: { data: string; contentType: string } | null = null;
    
          if (imageUrl) {
            imageInfo = await imageUrlToBase64(imageUrl);
            if (!imageInfo) {
              return {
                content: [
                  {
                    type: "text" as const,
                    text: `āŒ Failed to download image from URL: ${imageUrl}`,
                  },
                ],
                isError: true,
              };
            }
          } else if (imageData && imageContentType) {
            if (!isValidImageType(imageContentType)) {
              return {
                content: [
                  {
                    type: "text" as const,
                    text: `āŒ Unsupported image type: ${imageContentType}`,
                  },
                ],
                isError: true,
              };
            }
            imageInfo = { data: imageData, contentType: imageContentType };
          }
    
          if (imageInfo) {
            const uploadResult = await uploadImageAsHostedContent(
              graphService,
              teamId,
              channelId,
              imageInfo.data,
              imageInfo.contentType,
              imageFileName
            );
    
            if (uploadResult) {
              attachments.push(uploadResult.attachment);
            } else {
              return {
                content: [
                  {
                    type: "text" as const,
                    text: "āŒ Failed to upload image attachment",
                  },
                ],
                isError: true,
              };
            }
          }
        }
    
        // Build message payload
        const messagePayload: any = {
          body: {
            content,
            contentType,
          },
          importance,
        };
    
        if (finalMentions.length > 0) {
          messagePayload.mentions = finalMentions;
        }
    
        if (attachments.length > 0) {
          messagePayload.attachments = attachments;
        }
    
        const result = (await client
          .api(`/teams/${teamId}/channels/${channelId}/messages`)
          .post(messagePayload)) as ChatMessage;
    
        // Build success message
        const successText = `āœ… Message sent successfully. Message ID: ${result.id}${
          finalMentions.length > 0
            ? `\nšŸ“± Mentions: ${finalMentions.map((m) => m.mentionText).join(", ")}`
            : ""
        }${attachments.length > 0 ? `\nšŸ–¼ļø Image attached: ${attachments[0].name}` : ""}`;
    
        return {
          content: [
            {
              type: "text" as const,
              text: successText,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text" as const,
              text: `āŒ Failed to send message: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema validating parameters like teamId, channelId, message, optional importance, format, mentions array, and image attachment fields.
    {
      teamId: z.string().describe("Team ID"),
      channelId: z.string().describe("Channel ID"),
      message: z.string().describe("Message content"),
      importance: z.enum(["normal", "high", "urgent"]).optional().describe("Message importance"),
      format: z.enum(["text", "markdown"]).optional().describe("Message format (text or markdown)"),
      mentions: z
        .array(
          z.object({
            mention: z
              .string()
              .describe("The @mention text (e.g., 'john.doe' or 'john.doe@company.com')"),
            userId: z.string().describe("Azure AD User ID of the mentioned user"),
          })
        )
        .optional()
        .describe("Array of @mentions to include in the message"),
      imageUrl: z.string().optional().describe("URL of an image to attach to the message"),
      imageData: z.string().optional().describe("Base64 encoded image data to attach"),
      imageContentType: z
        .string()
        .optional()
        .describe("MIME type of the image (e.g., 'image/jpeg', 'image/png')"),
      imageFileName: z.string().optional().describe("Name for the attached image file"),
    },
  • MCP server.tool registration call that defines the tool name, description, input schema, and handler function.
    server.tool(
      "send_channel_message",
      "Send a message to a specific channel in a Microsoft Team. Supports text and markdown formatting, mentions, and importance levels.",
      {
        teamId: z.string().describe("Team ID"),
        channelId: z.string().describe("Channel ID"),
        message: z.string().describe("Message content"),
        importance: z.enum(["normal", "high", "urgent"]).optional().describe("Message importance"),
        format: z.enum(["text", "markdown"]).optional().describe("Message format (text or markdown)"),
        mentions: z
          .array(
            z.object({
              mention: z
                .string()
                .describe("The @mention text (e.g., 'john.doe' or 'john.doe@company.com')"),
              userId: z.string().describe("Azure AD User ID of the mentioned user"),
            })
          )
          .optional()
          .describe("Array of @mentions to include in the message"),
        imageUrl: z.string().optional().describe("URL of an image to attach to the message"),
        imageData: z.string().optional().describe("Base64 encoded image data to attach"),
        imageContentType: z
          .string()
          .optional()
          .describe("MIME type of the image (e.g., 'image/jpeg', 'image/png')"),
        imageFileName: z.string().optional().describe("Name for the attached image file"),
      },
      async ({
        teamId,
        channelId,
        message,
        importance = "normal",
        format = "text",
        mentions,
        imageUrl,
        imageData,
        imageContentType,
        imageFileName,
      }) => {
        try {
          const client = await graphService.getClient();
    
          // Process message content based on format
          let content: string;
          let contentType: "text" | "html";
    
          if (format === "markdown") {
            content = await markdownToHtml(message);
            contentType = "html";
          } else {
            content = message;
            contentType = "text";
          }
    
          // Process @mentions if provided
          const mentionMappings: Array<{ mention: string; userId: string; displayName: string }> = [];
          if (mentions && mentions.length > 0) {
            // Convert provided mentions to mappings with display names
            for (const mention of mentions) {
              try {
                // Get user info to get display name
                const userResponse = await client
                  .api(`/users/${mention.userId}`)
                  .select("displayName")
                  .get();
                mentionMappings.push({
                  mention: mention.mention,
                  userId: mention.userId,
                  displayName: userResponse.displayName || mention.mention,
                });
              } catch (_error) {
                console.warn(
                  `Could not resolve user ${mention.userId}, using mention text as display name`
                );
                mentionMappings.push({
                  mention: mention.mention,
                  userId: mention.userId,
                  displayName: mention.mention,
                });
              }
            }
          }
    
          // Process mentions in HTML content
          let finalMentions: Array<{
            id: number;
            mentionText: string;
            mentioned: { user: { id: string } };
          }> = [];
          if (mentionMappings.length > 0) {
            const result = processMentionsInHtml(content, mentionMappings);
            content = result.content;
            finalMentions = result.mentions;
    
            // Ensure we're using HTML content type when mentions are present
            contentType = "html";
          }
    
          // Handle image attachment
          const attachments: ImageAttachment[] = [];
          if (imageUrl || imageData) {
            let imageInfo: { data: string; contentType: string } | null = null;
    
            if (imageUrl) {
              imageInfo = await imageUrlToBase64(imageUrl);
              if (!imageInfo) {
                return {
                  content: [
                    {
                      type: "text" as const,
                      text: `āŒ Failed to download image from URL: ${imageUrl}`,
                    },
                  ],
                  isError: true,
                };
              }
            } else if (imageData && imageContentType) {
              if (!isValidImageType(imageContentType)) {
                return {
                  content: [
                    {
                      type: "text" as const,
                      text: `āŒ Unsupported image type: ${imageContentType}`,
                    },
                  ],
                  isError: true,
                };
              }
              imageInfo = { data: imageData, contentType: imageContentType };
            }
    
            if (imageInfo) {
              const uploadResult = await uploadImageAsHostedContent(
                graphService,
                teamId,
                channelId,
                imageInfo.data,
                imageInfo.contentType,
                imageFileName
              );
    
              if (uploadResult) {
                attachments.push(uploadResult.attachment);
              } else {
                return {
                  content: [
                    {
                      type: "text" as const,
                      text: "āŒ Failed to upload image attachment",
                    },
                  ],
                  isError: true,
                };
              }
            }
          }
    
          // Build message payload
          const messagePayload: any = {
            body: {
              content,
              contentType,
            },
            importance,
          };
    
          if (finalMentions.length > 0) {
            messagePayload.mentions = finalMentions;
          }
    
          if (attachments.length > 0) {
            messagePayload.attachments = attachments;
          }
    
          const result = (await client
            .api(`/teams/${teamId}/channels/${channelId}/messages`)
            .post(messagePayload)) as ChatMessage;
    
          // Build success message
          const successText = `āœ… Message sent successfully. Message ID: ${result.id}${
            finalMentions.length > 0
              ? `\nšŸ“± Mentions: ${finalMentions.map((m) => m.mentionText).join(", ")}`
              : ""
          }${attachments.length > 0 ? `\nšŸ–¼ļø Image attached: ${attachments[0].name}` : ""}`;
    
          return {
            content: [
              {
                type: "text" as const,
                text: successText,
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [
              {
                type: "text" as const,
                text: `āŒ Failed to send message: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'Supports text and markdown formatting, mentions, and importance levels' which describes capabilities but not behaviors. Critical behavioral aspects are missing: whether this is a mutating operation (implied but not stated), permission requirements, rate limits, error conditions, or what happens on success (e.g., returns message ID?). For a message-sending tool with 10 parameters, this is inadequate.

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

Conciseness4/5

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

The description is a single, efficient sentence that communicates the core purpose upfront. It wastes no words on redundancy or unnecessary elaboration. However, it could be more structured by separating purpose from capabilities for even clearer scanning.

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 complex mutation tool with 10 parameters, no annotations, and no output schema, the description is insufficient. It doesn't address critical context: mutation nature, authentication requirements, error handling, return values, or usage boundaries. The agent lacks enough information to use this tool confidently beyond basic parameter filling.

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%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema - it mentions 'text and markdown formatting' (covered by the 'format' enum), 'mentions' (covered by the 'mentions' array), and 'importance levels' (covered by the 'importance' enum). No additional semantic context is provided about parameter interactions or usage patterns.

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 message') and target ('to a specific channel in a Microsoft Team'), which is specific and actionable. It distinguishes from siblings like 'send_chat_message' by specifying 'channel' rather than 'chat', but doesn't explicitly contrast them. The mention of supported features (formatting, mentions, importance) adds useful detail about capabilities.

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 'send_chat_message' or 'reply_to_channel_message'. It mentions supported features but doesn't specify prerequisites, constraints, or typical use cases. The agent must infer usage from the tool name and parameter names 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/floriscornel/teams-mcp'

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