Twist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

create-conversation

Start a direct or group conversation with selected users and post an initial message, reusing an existing conversation for the same set of users to avoid duplicates.

Instructions

Start a direct or group conversation with one or more users and post an initial message. Reuses the existing conversation if one already exists for the same set of users.

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": {
      "workspaceId": "<workspaceId>",
      "recipients": "<recipients>",
      "content": "<content>"
    },
    "name": "create-conversation"
  }
}

Input Schema

Name	Required	Description
`content`	Yes	The content of the first message to post.
`recipients`	Yes	User IDs to include in the direct or group conversation (excluding yourself, who is added automatically). Use get-users to resolve names to IDs.
`workspaceId`	Yes	The ID of the workspace the conversation belongs to.

Output Schema

Name	Required	Description	Default
`type`	Yes
`content`	Yes
`created`	Yes
`success`	Yes
`messageId`	Yes
`messageUrl`	Yes
`recipients`	Yes
`workspaceId`	Yes
`participants`	Yes
`conversationId`	Yes
`conversationUrl`	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"

Addedv5.6.0Jul 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations by explaining that an existing conversation with the same users is reused rather than creating a duplicate. It also transparently states the side effect of posting an initial message. The annotations already convey read/write safety, so no contradiction exists.

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. It front-loads the primary action and scope, then adds the reuse behavior as a concise, useful secondary sentence.

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, schema, and annotations together cover what the tool does, its side effects, and its parameters, and an output schema exists to document return values. The only minor gap is not explicitly distinguishing this tool from create-thread in the same workspace context, but this is not a major omission.

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 parameters are fully documented in the input schema. The description itself does not add extra semantic detail beyond what the schema already provides, which is acceptable but not above the baseline.

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 ('Start'), names the exact resource ('direct or group conversation'), and states the additional behavior of posting an initial message. It also clearly differentiates from the sibling create-thread by scoping to one-on-one/group conversations.

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 clearly indicates when to use this tool: when starting a direct or group conversation and posting an initial message. It also adds the important context that existing conversations are reused. It does not explicitly name alternatives or exclusions, but the core usage context is clear.

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