Skip to main content
Glama
Doist

Twist AI MCP Server

Official
by Doist

create-thread

Create a new thread in a Twist workspace channel by providing the channel ID, title, and content. Optionally notify specific users or groups.

Instructions

Create a new thread in a workspace channel. Requires a channel ID, title, and content. Optionally notify specific users or groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe title of the thread.
groupsNoOptional array of group IDs to notify. Use get-groups to discover group IDs before passing them here.
contentYesThe content/body of the thread.
channelIdYesThe ID of the channel to create the thread in.
recipientsNoOptional array of user IDs to notify. If omitted, Twist defaults to notifying all current members of the channel (equivalent to the API's "EVERYONE" default). Note: workspace users who have not joined this channel will not be notified — add their IDs explicitly if you want to reach them.
displayInInboxNoIf true, unarchives the thread after creation so it appears in the author's Inbox. Defaults to false. Can also be enabled for all calls by setting the TWIST_CREATE_THREAD_DISPLAY_IN_INBOX=true environment variable (local MCP only).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
titleYes
groupsNo
contentYes
createdYes
creatorYes
successYes
threadIdYes
channelIdYes
threadUrlYes
recipientsNo
workspaceIdYes
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive. Description adds 'Create a new thread' confirming mutation but no additional behavioral traits beyond the schema. Adequate but not enhanced.

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, no redundant words. Front-loaded with action and requirements.

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?

Covers core function and optional inputs. Output schema exists so return values are documented. Lacks mention of error handling or prerequisites, but still sufficient for typical usage.

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 100% with detailed parameter descriptions. Description restates required params and optional notification but does not add significant meaning beyond what schema already provides. Baseline score of 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?

Clearly states it creates a new thread in a workspace channel, specifying required and optional inputs. Differentiates from sibling tools like load-thread (reading) and reply (responding).

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?

Explicitly states requirements (channel ID, title, content) and optional users/groups notification. Does not mention when not to use or compare with alternatives, but for a creation tool, guidance is clear and sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Doist/twist-ai'

If you have feedback or need assistance with the MCP directory API, please join our Discord server