Twist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

react

Destructive

Manage emoji reactions on Twist threads, comments, or messages. Specify the target type and ID to add or remove an emoji.

Instructions

Add or remove an emoji reaction on a thread, comment, or conversation message. Use targetType to specify the type of object (thread, comment, or message) and targetId for the 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": {
      "targetType": "<targetType>",
      "targetId": "<targetId>",
      "emoji": "<emoji>"
    },
    "name": "react"
  }
}

Input Schema

Name	Required	Description	Default
`emoji`	Yes	The emoji to react with (e.g., "👍", "❤️", "🎉").
`targetId`	Yes	The ID of the thread, comment, or message to react to.
`operation`	No	Whether to add or remove the reaction.	add
`targetType`	Yes	The type of object to react to: thread, comment, or message.

Output Schema

Name	Required	Description	Default
`type`	Yes
`emoji`	Yes
`success`	Yes
`targetId`	Yes
`operation`	Yes
`targetUrl`	Yes
`targetType`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv7.0.0Aug 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv5.5.1Jul 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already indicate the tool is read/write, non-idempotent, and destructive, so the description doesn't contradict them. The description adds context about target types, but it does not disclose behavior such as whether adding an existing reaction replaces it, whether removal is idempotent, or what the response contains. Given annotation coverage, a mid-range score is appropriate.

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?

Two concise sentences with no filler. The action and target types are front-loaded, and the pointer to targetType/targetId is efficient and directly useful.

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?

The description, combined with a complete input schema and output schema, covers the essential information an agent needs to select and invoke the tool. It could mention the operation default or enum, but the schema already documents those details, so nothing critical is missing.

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%, so the baseline is 3. The description adds minimal value beyond the schema by restating targetType/targetId roles, but it does not introduce new parameter details or usage nuances.

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 action—'Add or remove an emoji reaction'—and names the resource types explicitly (thread, comment, conversation message). It clearly differentiates the tool from siblings like reply, delete-object, or update-object by focusing on emoji reactions.

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?

Provides clear context on when to use the tool: whenever an emoji reaction needs to be added or removed on a thread, comment, or message. It does not explicitly name alternatives or exclusions, but none of the sibling tools target reactions, so the usage scope is adequately defined.

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