Enterprise Threads MCP Server

create_reply

Reply to a specific thread or post with text or media, and control who can reply to your reply.

Instructions

Reply to a specific thread/post

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": {
      "reply_to_id": "<reply_to_id>",
      "text": "<text>"
    },
    "name": "create_reply"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Reply text content
`media_url`	No	URL of media to include (for IMAGE/VIDEO)
`media_type`	No	Type of media (default: TEXT)
`reply_to_id`	Yes	ID of the thread/post to reply to
`reply_control`	No	Who can reply to this reply

Schema Changelog

Changes observed during successful MCP inspections.

First observedv5.1.0Aug 14, 2026

TDQS

C2.9/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 only states 'Reply to a specific thread/post' and does not explain whether this creates a new reply, whether it can be scheduled, how reply_control affects visibility, or what response the caller should expect. This is a significant gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words, and the core action is front-loaded. However, it is so brief that it sacrifices valuable explanatory content that could be provided without bloating the description.

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?

With no annotations and no output schema, the description must compensate, but it does not. It lacks context about the reply creation process, constraints, media handling, or return values. Given the 5-parameter schema and many sibling tools, more detail is needed for the agent to invoke this correctly.

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 documents all five parameters, including enums for media_type and reply_control. The description adds no extra parameter context, but the baseline of 3 is appropriate because the structured data is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Reply') and the resource ('a specific thread/post'), making the core purpose obvious. It is not distinguished from sibling tools like manage_reply or quote_post, but it is specific enough to convey the intended operation.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. The description implies usage for replying to threads/posts but does not mention exclusions, prerequisites, or when manage_reply or quote_post would be more appropriate.

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

Deploy Server