Skip to main content
Glama

Post Teams Channel Message

send_channel_message
Destructive

Posts a message to a Microsoft Teams channel or replies within an existing thread. Use it to share updates, steps, or structured markdown content with a team.

Instructions

Send a message to a Teams channel, or reply in a thread with reply_to_message_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": {
      "team_id": "<team_id>",
      "channel_id": "<channel_id>",
      "content": "<content>"
    },
    "name": "send_channel_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo'text' (default) sends content as typed. 'markdown' formats it: **bold**, *italic*, `code`, ``` code blocks ```, '- ' and '1. ' lists, # headings and [links](https://…). Use markdown for steps, commands or anything with structure. Markdown is capped at 30,000 characters.
contentYesMessage content
team_idYesTeam ID
channel_idYesChannel ID
reply_to_message_idNoID of a top-level channel message to reply to, from list_channel_messages. Omit to start a new thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/destructive profile is covered by structured data. The description adds no behavioral context beyond that — no mention of what sending does to the channel, whether messages can be edited/unsent, rate limits, or permission requirements. It is consistent with the annotations (a send is a write), so no contradiction.

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?

A single tight sentence that front-loads the primary action and appends the secondary thread-reply mode. Nothing is wasted, though the trailing clause largely duplicates schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation tool with no output schema, the description omits what a successful call returns (e.g., the new message ID needed for follow-up replies) and any error/permission conditions. It is minimally adequate for correct invocation but not complete.

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%, including detailed guidance on the format enum and explicit 'omit to start a new thread' semantics for reply_to_message_id. The description only restates that parameter's name, adding no meaning beyond the schema; the baseline 3 applies.

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?

Uses a specific verb and resource ('Send a message to a Teams channel') and adds the thread-reply variant, so the agent knows exactly what the tool does. It does not name distinguishing siblings such as send_chat_message, leaving the channel-vs-chat boundary implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a usable conditional hint for the reply case ('reply in a thread with reply_to_message_id'), but says nothing about when to choose this over send_chat_message or send_message, nor about preconditions like team/channel membership.

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