mcp-saas-toolkit

slack_add_reaction

Add an emoji reaction to a Slack message to acknowledge, approve, or update status. Specify channel, timestamp, and emoji name.

Instructions

Add an emoji reaction to a Slack message. Useful for acknowledgements, approvals, or status updates.

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": {
      "channel": "<channel>",
      "timestamp": "<timestamp>",
      "name": "<name>"
    },
    "name": "slack_add_reaction"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Emoji name without colons (e.g. 'thumbsup', 'white_check_mark', 'rocket')
`channel`	Yes	Channel ID containing the message
`timestamp`	Yes	Timestamp (ts) of the message to react to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 29, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic action and use cases, omitting details like permissions, idempotency, error handling, or side effects. The parameter descriptions in the schema cover syntax but not behavior.

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?

The description is two sentences with no wasted words. The action is front-loaded, and the second sentence provides context. Highly concise.

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 simple 3-parameter action with no output schema, the description covers the purpose and usage context. However, it lacks details on duplicate reactions, rate limits, or authentication, which slightly reduces completeness.

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%, with each parameter having a clear description (e.g., 'Emoji name without colons'). The tool description adds no additional meaning beyond the schema, so baseline score 3 applies.

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 clearly states 'Add an emoji reaction to a Slack message' with a specific verb and resource. It also lists example use cases, distinguishing it from sibling tools like slack_send_message or slack_set_topic.

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?

The description mentions use cases (acknowledgements, approvals, status updates) but does not explicitly state when not to use it or compare to alternatives. However, the context of sibling tools makes the distinction clear.

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