Skip to main content
Glama
Sign In
Enterprise Threads MCP Server

Enterprise Threads MCP Server

by baguskto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_thread_chain

Create a thread chain by posting multiple connected replies to a parent thread, enabling a structured conversation in one operation.

Instructions

Create a thread chain (multiple connected replies)

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": {
      "parent_thread_id": "<parent_thread_id>",
      "replies": "<replies>"
    },
    "name": "create_thread_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
repliesYesArray of reply texts to create as a chain
parent_thread_idYesID of the parent thread to start the chain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only the basic action and does not mention side effects, permissions, rate limits, or what occurs on failure. As a mutation tool, this lack of detail is a significant gap.

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 a single, concise sentence that front-loads the verb and resource. Every word contributes, and there is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema and no annotations. The description does not mention return values, side effects, or usage limitations. While the input schema is well-defined, the overall definition is too sparse for an agent to fully anticipate the tool's behavior and results.

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%: both parent_thread_id and replies have descriptions that explain their roles. The tool description adds little beyond confirming that replies are connected; the schema already provides the necessary parameter meaning.

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 specifies the action ('Create') and the resource ('a thread chain'), and the parenthetical '(multiple connected replies)' clarifies what the tool does. This distinguishes it from sibling tools like create_reply (single reply) and publish_thread (creating a new thread).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating multiple connected replies, but it offers no explicit guidance on when to choose this tool over alternatives like create_reply or publish_thread. No when-not-to-use conditions or alternative tool names are mentioned.

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

Deploy Server

Other Tools