Skip to main content
Glama

graph_react_to_message

Set or remove an emoji reaction on a Microsoft Teams chat or channel message by supplying the message ID and either chat ID or team/channel IDs.

Instructions

Set or remove an emoji reaction on a chat or channel message.

Supply either chat_id for a chat message or both team_id and channel_id for a channel message, never both.

Args: message_id: The message ID to react to. chat_id: Chat ID for a chat message. Empty when targeting a channel. team_id: Team ID for a channel message. Empty when targeting a chat. channel_id: Channel ID for a channel message. Empty when targeting a chat. reaction: Reaction type (default "like"). Common: like, heart, laugh, surprised, sad, angry. remove: Whether to remove the reaction instead of setting it (default false).

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>"
    },
    "name": "graph_react_to_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
removeNo
chat_idNo
team_idNo
reactionNolike
channel_idNo
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool can both set and remove reactions, includes defaults for reaction and remove, and lists common reaction values, but it does not mention permissions, rate limits, reversibility, or error behavior beyond the targeting constraint.

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 front-loaded with a clear one-sentence purpose and then uses an Args section for details. It is appropriately sized, though the repeated 'Empty when targeting...' phrasing for chat_id, team_id, and channel_id is slightly verbose.

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?

For a six-parameter mutation tool with no annotations and no output schema, the description covers the essential behavior: setting versus removing a reaction, default reaction, common reaction values, and the chat-versus-channel targeting rule. It does not describe authentication, permissions, or response behavior, but the core invocation semantics are complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 supply parameter meaning, and it does: it documents every parameter, including message_id, the mutually exclusive chat/channel targeting fields, the default reaction value, common reaction types, and the remove flag.

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?

The description states a specific verb and resource: set or remove an emoji reaction on a chat or channel message. It clearly distinguishes the two targeting modes (chat_id versus team_id plus channel_id), so the tool's purpose is immediately understandable.

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?

It gives explicit targeting rules: supply either chat_id for a chat message or both team_id and channel_id for a channel message, never both. It does not name alternative sibling tools or explain when to prefer this over them, but the primary usage condition is clear.

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