Skip to main content
Glama

Coline

React to message

react_to_message

Adds the person's emoji reaction to a message, or takes it back if they'd already reacted with it.

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": {
      "workspace": "<workspace>",
      "messageId": "<messageId>",
      "emoji": "<emoji>"
    },
    "name": "react_to_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
emojiYesAn emoji, e.g. 👍.
reactedNotrue adds it, false takes it back; leave it out to toggle.
messageIdYesMessage id from read_conversation.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdNoFrom list_conversations.

Output Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the default call is a toggle that may REMOVE an existing reaction, which is a side effect an agent must anticipate. It stops short of saying what happens on repeat calls or whether reactions are visible to others, so it is not a 5.

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?

A single front-loaded sentence with no filler; the add behavior is stated first and the take-back case follows. Nothing could be removed without losing meaning.

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 schema covers most parameters. What remains thin is the interaction with the 'reacted' flag and the message-type scope, but for a simple reaction tool the description plus structured fields are close to sufficient.

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 coverage is 83% and the schema already documents emoji, reacted, messageId, workspace and conversationId in detail. The description only echoes the toggle meaning that the 'reacted' parameter already explains, and says nothing about the type enum (channel/dm/task) or the workspace/conversationId requirements. Baseline 3 is appropriate given the schema does the heavy lifting.

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 states a specific verb and resource (add/remove an emoji reaction on a message) and correctly captures the dual add/remove nature of the operation. It does not differentiate itself from any sibling (e.g. pin_message or save_message), but the purpose is unambiguous on its own.

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?

Usage is only implied: an agent can infer it should call this when it wants to react to a message, and the 'takes it back if they'd already reacted' clause hints at toggle semantics. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention that 'reacted' can be used to make the intent explicit rather than relying on the toggle.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources