Twist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

reply

Post comments to threads or messages to conversations, with optional notifications to specific users, groups, or a channel/thread audience.

Instructions

Post a reply to a thread (as a comment) or conversation (as a message). Thread replies notify everyone who has interacted with the thread by default unless specific user recipients, groups, or a notifyAudience are provided.

Input Schema

TableJSON Schema

Name	Required	Description
`groups`	No	Optional array of group IDs to notify (only for thread replies). Use get-groups to discover group IDs before passing them here.
`content`	Yes	The content of the reply.
`targetId`	Yes	The ID of the thread or conversation to reply to.
`recipients`	No	Optional array of user IDs to notify (only for thread replies). If omitted with no groups and no notifyAudience, thread replies default to notifying everyone who has interacted with the thread.
`targetType`	Yes	The type of object to reply to: thread (posts a comment) or conversation (posts a message).
`notifyAudience`	No	Optional broader audience to notify in addition to recipients and groups (only for thread replies). 'channel' notifies everyone in the channel; 'thread' notifies everyone who has interacted with the thread.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes
`groups`	No
`content`	Yes
`created`	Yes
`replyId`	Yes
`success`	Yes
`replyUrl`	Yes
`targetId`	Yes
`recipients`	No
`targetType`	Yes
`notifyAudience`	No

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.2/5.0

Behavior4/5

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

Beyond the annotations, the description discloses a meaningful side effect: thread replies notify all thread participants by default unless recipients, groups, or notifyAudience are provided. This is valuable behavior information for an agent deciding on notification impact.

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 tight sentences, with the primary action stated first and the notification behavior following. Every word earns its place, and there is no redundant filler.

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 the well-covered schema and output schema, gives an agent enough to call the tool correctly. It captures the core dual behavior and the notification side effect, though it could explicitly mention how to discover user/group IDs beyond what the schema already notes for groups.

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 schema already explains each parameter. The description adds a concise summary of the notification default, but it does not meaningfully expand on what the schema already provides.

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 uses a specific verb and resource: 'Post a reply to a thread (as a comment) or conversation (as a message).' It clearly distinguishes the tool's operation from sibling tools like create-thread or create-conversation by focusing on replying to existing objects.

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 makes it clear this tool is for replying to existing threads or conversations, which implies when it should be used rather than creating new content. It adds notification-default context that helps with optional parameters, but it does not explicitly name alternatives or state when not to use it.

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