longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Create Topic Reply

topic_create_reply

Post a reply to a discussion topic. Use reply_to_id to nest under a specific comment, or omit for a top-level response.

Instructions

Create a reply to a discussion topic. Pass reply_to_id to nest under another reply; omit for a top-level reply.

Input Schema

TableJSON Schema

Name	Required	Description
`_jq`	No	Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data \| map({symbol}). Omit for the full response.
`body`	Yes	Reply body (plain text only).
`topic_id`	Yes	Topic ID to reply to.
`reply_to_id`	No	Optional parent reply ID for nested replies. Get IDs from `topic_replies`. Omit for a top-level reply.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.12.0Sep 23, 2026

addedInput schema / properties / _jq / description

Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "TopicAuthor": {
-      "properties": {
-        "avatar": {
-          "type": "string"
-        },
-        "member_id": {
-          "type": "string"
-        },
-        "name": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "member_id",
-        "name",
-        "avatar"
-      ],
-      "type": "object"
-    },
-    "TopicImage": {
-      "properties": {
-        "lg": {
-          "type": "string"
-        },
-        "sm": {
-          "type": "string"
-        },
-        "url": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "url",
-        "sm",
-        "lg"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "author": {
-      "$ref": "#/$defs/TopicAuthor"
-    },
-    "body": {
-      "type": "string"
-    },
-    "comments_count": {
-      "format": "int32",
-      "type": "integer"
-    },
-    "created_at": {
-      "type": "string"
-    },
-    "id": {
-      "type": "string"
-    },
-    "images": {
-      "items": {
-        "$ref": "#/$defs/TopicImage"
-      },
-      "type": "array"
-    },
-    "likes_count": {
-      "format": "int32",
-      "type": "integer"
-    },
-    "reply_to_id": {
-      "type": "string"
-    },
-    "topic_id": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "id",
-    "topic_id",
-    "body",
-    "reply_to_id",
-    "author",
-    "images",
-    "likes_count",
-    "comments_count",
-    "created_at"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"TopicCreateReplyParam"
```
Changed20 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $defs / TopicAuthor / description
```
Removed value: -"Author of a topic or reply."
```
- removedOutput schema / $defs / TopicAuthor / properties / avatar / description
```
Removed value: -"Avatar URL."
```
- removedOutput schema / $defs / TopicAuthor / properties / member_id / description
```
Removed value: -"Member ID."
```
- removedOutput schema / $defs / TopicAuthor / properties / name / description
```
Removed value: -"Display name."
```
- removedOutput schema / $defs / TopicImage / description
```
Removed value: -"An image attached to a topic or reply."
```
- removedOutput schema / $defs / TopicImage / properties / lg / description
```
Removed value: -"Large image URL."
```
- removedOutput schema / $defs / TopicImage / properties / sm / description
```
Removed value: -"Small thumbnail URL."
```
- removedOutput schema / $defs / TopicImage / properties / url / description
```
Removed value: -"Original image URL."
```
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `topic_create_reply`. The created reply.\n\nSDK-typed (`longbridge::content::TopicReply`) and serialized via `tool_json`.\n`created_at` is emitted as an RFC3339 string."
```
- removedOutput schema / properties / author / description
```
Removed value: -"Reply author."
```
- removedOutput schema / properties / body / description
```
Removed value: -"Reply body (plain text)."
```
- removedOutput schema / properties / comments_count / description
```
Removed value: -"Nested replies count."
```
- removedOutput schema / properties / created_at / description
```
Removed value: -"Created time (RFC3339)."
```
- removedOutput schema / properties / id / description
```
Removed value: -"Reply ID."
```
- removedOutput schema / properties / images / description
```
Removed value: -"Attached images."
```
- removedOutput schema / properties / likes_count / description
```
Removed value: -"Likes count."
```
- removedOutput schema / properties / reply_to_id / description
```
Removed value: -"Parent reply ID (`\"0\"` means top-level)."
```
- removedOutput schema / properties / topic_id / description
```
Removed value: -"Topic ID this reply belongs to."
```
- removedOutput schema / title
```
Removed value: -"TopicCreateReplyResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "TopicAuthor": {
+      "description": "Author of a topic or reply.",
+      "properties": {
+        "avatar": {
+          "description": "Avatar URL.",
+          "type": "string"
+        },
+        "member_id": {
+          "description": "Member ID.",
+          "type": "string"
+        },
+        "name": {
+          "description": "Display name.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "member_id",
+        "name",
+        "avatar"
+      ],
+      "type": "object"
+    },
+    "TopicImage": {
+      "description": "An image attached to a topic or reply.",
+      "properties": {
+        "lg": {
+          "description": "Large image URL.",
+          "type": "string"
+        },
+        "sm": {
+          "description": "Small thumbnail URL.",
+          "type": "string"
+        },
+        "url": {
+          "description": "Original image URL.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "url",
+        "sm",
+        "lg"
+      ],
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `topic_create_reply`. The created reply.\n\nSDK-typed (`longbridge::content::TopicReply`) and serialized via `tool_json`.\n`created_at` is emitted as an RFC3339 string.",
+  "properties": {
+    "author": {
+      "$ref": "#/$defs/TopicAuthor",
+      "description": "Reply author."
+    },
+    "body": {
+      "description": "Reply body (plain text).",
+      "type": "string"
+    },
+    "comments_count": {
+      "description": "Nested replies count.",
+      "format": "int32",
+      "type": "integer"
+    },
+    "created_at": {
+      "description": "Created time (RFC3339).",
+      "type": "string"
+    },
+    "id": {
+      "description": "Reply ID.",
+      "type": "string"
+    },
+    "images": {
+      "description": "Attached images.",
+      "items": {
+        "$ref": "#/$defs/TopicImage"
+      },
+      "type": "array"
+    },
+    "likes_count": {
+      "description": "Likes count.",
+      "format": "int32",
+      "type": "integer"
+    },
+    "reply_to_id": {
+      "description": "Parent reply ID (`\"0\"` means top-level).",
+      "type": "string"
+    },
+    "topic_id": {
+      "description": "Topic ID this reply belongs to.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "topic_id",
+    "body",
+    "reply_to_id",
+    "author",
+    "images",
+    "likes_count",
+    "comments_count",
+    "created_at"
+  ],
+  "title": "TopicCreateReplyResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the description doesn't need to restate mutation. It adds useful context about nesting behavior and plain-text body, but doesn't disclose things like whether the reply is immediately visible, whether editing/deleting is possible, or any rate limits. With annotations covering the safety profile, a 3 is appropriate.

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 sentences, zero filler. The primary action and the critical branching instruction (reply_to_id vs omit) are front-loaded. Every word earns its place.

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?

For a create-reply tool with full schema coverage and annotations indicating a non-read, non-idempotent write, the description covers the essential call pattern. It doesn't describe the response shape, but there is no output schema and the tool's purpose is straightforward. The only minor gap is not stating what happens on success (e.g., returned reply ID), but that is not critical for invoking it 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 four parameters. The description adds the key semantic distinction for reply_to_id (nest vs top-level) and clarifies body is plain text, but it doesn't add meaning beyond what the schema already provides. Baseline 3 is correct.

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 states a specific verb ('Create') and resource ('a reply to a discussion topic'), and immediately distinguishes the two call modes: nested (reply_to_id) vs top-level (omit). This clearly differentiates it from siblings like topic_create and topic_replies.

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 gives explicit guidance on when to pass reply_to_id versus omit it, and the schema's reply_to_id description points to topic_replies for obtaining parent IDs. It doesn't explicitly say when to prefer this over topic_create, but the context is clear enough for a discussion-reply tool.

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

Deploy Server

Create Topic Reply

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools