Skip to main content
Glama
longbridge

longbridge

Official

Create Topic Reply

topic_create_reply

Create a reply to a discussion topic. Provide the topic ID and body text; optionally set a parent reply ID to nest the reply under an existing comment.

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
NameRequiredDescriptionDefault
bodyYesReply body (plain text only).
topic_idYesTopic ID to reply to.
reply_to_idNoOptional parent reply ID for nested replies. Get IDs from `topic_replies`. Omit for a top-level reply.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
bodyYes
authorYes
imagesYes
topic_idYes
created_atYes
likes_countYes
reply_to_idYes
comments_countYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"TopicCreateReplyParam"
  2. Changed20 schema fields changedv0.6.0
    • 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"
  3. Changed1 schema field changedv0.5.6
    • 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"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. First observedv0.1.12

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already indicate it is not read-only or destructive. The description adds no further behavioral details (e.g., auth requirements, duplicate handling). It is consistent with annotations, so a baseline score 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 clear sentences with no unnecessary words. Front-loaded with the main action, followed by parameter guidance.

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

Completeness5/5

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

Given the presence of an output schema and the simple nature of the tool, the description covers all necessary context: what it does, required parameters, and optional usage. Sibling tools are numerous but not relevant to completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by explaining the semantics of reply_to_id (nesting vs. top-level) beyond the schema description, which already references getting IDs from topic_replies.

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 states the tool creates a reply to a discussion topic, distinguishing it from sibling tools like topic_create (creates topic) and topic_replies (lists 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?

Provides clear guidance on when to use the optional reply_to_id parameter for nesting, but does not explicitly state when to use this tool over alternatives. However, the context is clear for a reply creation tool.

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/longbridge/longbridge-mcp'

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