teams-mcp-server

Overview Schema Source Related Servers Discussions Admin

unset_reaction

Remove a reaction from a Microsoft Teams channel or chat message by supplying the message ID and reaction, plus team/channel or chat IDs. Channel thread replies not supported.

Instructions

Remove a reaction from a message.

For channel messages: provide team_id + channel_id + message_id. For chat messages: provide chat_id + message_id. Works on top-level channel messages and on chat messages; channel thread replies are not supported (Graph addresses them under their parent message).

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": {
      "message_id": "<message_id>",
      "reaction": "<reaction>"
    },
    "name": "unset_reaction"
  }
}

Input Schema

Name	Required	Description	Default
`chat_id`	No
`team_id`	No
`reaction`	Yes
`channel_id`	No
`message_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Oct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose a genuinely non-obvious constraint: thread replies are unsupported because Graph addresses them under the parent message. It does not cover permissions, idempotency when the reaction is absent, or error behavior, so gaps remain.

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?

Purpose is front-loaded in one short sentence, followed by compact routing rules and a scope caveat. Every sentence earns its place, with only mild redundancy between the chat-routing line and the scope sentence.

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

Completeness4/5

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

An output schema exists so return values need no explanation, and the routing plus thread-reply exclusion cover the main ambiguity for a 5-parameter tool. The missing reaction-format detail and absence of any permission/idempotency note leave a small but real gap.

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 0%, so the description must compensate, and it does explain the conditional required combinations of team_id/channel_id/chat_id/message_id. However it never describes the required 'reaction' parameter's expected format (emoji, name, unicode), which is the single most error-prone input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Remove a reaction from a message'), and the removal semantics are inherently distinguished from the sibling set_reaction. An agent can identify the tool without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit conditional routing (channel messages need team_id + channel_id + message_id; chat messages need chat_id + message_id) and a clear exclusion (channel thread replies not supported). It stops short of naming the complementary sibling set_reaction or stating prerequisites, so it is strong but not exhaustive.

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