Skip to main content
Glama
longbridge

longbridge

Official

Topic Detail

topic_detail
Read-onlyIdempotent

Retrieve full discussion topic details by supplying the topic ID. Access content and metadata for any discussion.

Instructions

Get discussion topic detail by topic_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topic_idYesTopic ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
bodyYes
titleYes
authorYes
imagesYes
tickersYes
hashtagsYes
created_atYes
detail_urlYes
topic_typeYes
updated_atYes
descriptionYes
likes_countYes
views_countYes
shares_countYes
comments_countYes

Schema Changelog

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

  1. Changed2 schema fields changedv0.8.7
    • addedOutput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / title
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"TopicIdParam"
  3. Changed27 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_detail`. Full details of a single community topic.\n\nSDK-typed (`longbridge::content::OwnedTopic`) and serialized via `tool_json`.\n`created_at` / `updated_at` are emitted as RFC3339 strings."
    • removedOutput schema / properties / author / description
      Removed value: -"Topic author."
    • removedOutput schema / properties / body / description
      Removed value: -"Markdown body."
    • removedOutput schema / properties / comments_count / description
      Removed value: -"Comments count."
    • removedOutput schema / properties / created_at / description
      Removed value: -"Created time (RFC3339)."
    • removedOutput schema / properties / description
      Removed value: -{
      -  "description": "Plain-text excerpt / description.",
      -  "type": "string"
      -}
    • removedOutput schema / properties / detail_url / description
      Removed value: -"URL to the full topic page."
    • removedOutput schema / properties / hashtags / description
      Removed value: -"Hashtag names."
    • removedOutput schema / properties / id / description
      Removed value: -"Topic ID."
    • removedOutput schema / properties / images / description
      Removed value: -"Attached images."
    • removedOutput schema / properties / likes_count / description
      Removed value: -"Likes count."
    • removedOutput schema / properties / shares_count / description
      Removed value: -"Shares count."
    • removedOutput schema / properties / tickers / description
      Removed value: -"Related stock tickers, format `<CODE>.<MARKET>` (e.g. \"TSLA.US\")."
    • removedOutput schema / properties / title
      Removed value: -{
      -  "description": "Title.",
      -  "type": "string"
      -}
    • removedOutput schema / properties / topic_type / description
      Removed value: -"Content type: \"article\" or \"post\"."
    • removedOutput schema / properties / updated_at / description
      Removed value: -"Last updated time (RFC3339)."
    • removedOutput schema / properties / views_count / description
      Removed value: -"Views count."
    • removedOutput schema / title
      Removed value: -"TopicDetailResponse"
  4. 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_detail`. Full details of a single community topic.\n\nSDK-typed (`longbridge::content::OwnedTopic`) and serialized via `tool_json`.\n`created_at` / `updated_at` are emitted as RFC3339 strings.",
      +  "properties": {
      +    "author": {
      +      "$ref": "#/$defs/TopicAuthor",
      +      "description": "Topic author."
      +    },
      +    "body": {
      +      "description": "Markdown body.",
      +      "type": "string"
      +    },
      +    "comments_count": {
      +      "description": "Comments count.",
      +      "format": "int32",
      +      "type": "integer"
      +    },
      +    "created_at": {
      +      "description": "Created time (RFC3339).",
      +      "type": "string"
      +    },
      +    "description": {
      +      "description": "Plain-text excerpt / description.",
      +      "type": "string"
      +    },
      +    "detail_url": {
      +      "description": "URL to the full topic page.",
      +      "type": "string"
      +    },
      +    "hashtags": {
      +      "description": "Hashtag names.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "id": {
      +      "description": "Topic ID.",
      +      "type": "string"
      +    },
      +    "images": {
      +      "description": "Attached images.",
      +      "items": {
      +        "$ref": "#/$defs/TopicImage"
      +      },
      +      "type": "array"
      +    },
      +    "likes_count": {
      +      "description": "Likes count.",
      +      "format": "int32",
      +      "type": "integer"
      +    },
      +    "shares_count": {
      +      "description": "Shares count.",
      +      "format": "int32",
      +      "type": "integer"
      +    },
      +    "tickers": {
      +      "description": "Related stock tickers, format `<CODE>.<MARKET>` (e.g. \"TSLA.US\").",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "title": {
      +      "description": "Title.",
      +      "type": "string"
      +    },
      +    "topic_type": {
      +      "description": "Content type: \"article\" or \"post\".",
      +      "type": "string"
      +    },
      +    "updated_at": {
      +      "description": "Last updated time (RFC3339).",
      +      "type": "string"
      +    },
      +    "views_count": {
      +      "description": "Views count.",
      +      "format": "int32",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "title",
      +    "description",
      +    "body",
      +    "author",
      +    "tickers",
      +    "hashtags",
      +    "images",
      +    "likes_count",
      +    "comments_count",
      +    "views_count",
      +    "shares_count",
      +    "topic_type",
      +    "detail_url",
      +    "created_at",
      +    "updated_at"
      +  ],
      +  "title": "TopicDetailResponse",
      +  "type": "object"
      +}
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description is consistent with these annotations but adds no extra behavioral context such as error handling, response limitations, or auth requirements. With annotations present, this is adequate but not enriching.

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, front-loaded sentence with no filler. Every word contributes to understanding the tool's purpose and key parameter.

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 simple read-only lookup tool with one required parameter, an output schema, and strong annotations, the description is largely sufficient. It lacks any note about behavior for invalid/missing topic IDs or explicit relationship with sibling topic tools, but these are minor gaps given the tool's simplicity.

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%, and the only parameter topic_id is self-explanatory. The description's 'by topic_id' reinforces the parameter's role but adds no additional semantics, format constraints, or edge-case context beyond the schema.

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 operation: 'Get discussion topic detail by topic_id.' It names a specific verb and resource, making the purpose obvious. However, it does not explicitly differentiate from sibling tools like 'topic' or 'topic_replies', so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives such as 'topic_search', 'topic_replies', or 'topic'. The description only states what the tool does without providing context, prerequisites, or alternative tool references.

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