# WeChat Official Accounts MP comment replies

Get the second-level replies under a first-level comment. Needs url. Served by TikHub.

Purpose:
- Get the second-level replies under a first-level comment.
- Chain: first call `fetch_article_comments` to get each comment's `content_id`, then feed it into this endpoint.
- ⏱️ Due to WeChat server latency, this endpoint responds slowly; please set your client request timeout to 30 seconds — a timeout that is too small may result in being billed without receiving the response.
- ⚠️ Large-integer ID precision: IDs such as `content_id` / `reply_id` in the response are 64-bit big integers beyond JavaScript's safe-integer range (2^53-1). Always receive / pass such IDs as **strings** (parse JSON with json-bigint or read them as text), never through JS `Number`. Swagger UI rounds the trailing digits of huge integers in its docs view — this is expected and does not affect the actual data returned by the API.
Parameters:
- url: WeChat MP article URL (`https://mp.weixin.qq.com/s/…`). E.g. `http://mp.weixin.qq.com/s?__biz=Mzk3NTA0MzM5NA==&mid=2247483745&idx=1&sn=3f34e768cf457a501038991ed30be1f4rd`
- content_id: Optional (numeric). `content_id` of the target first-level comment, from `$.data.comments[N].content_id` of the `fetch_article_comments` response; **defaults to the first comment that has replies when omitted**. E.g. `12109128638545265979`
- offset: Optional, default 0 (>=0). Reply pagination offset; 0 for the first page, pass `next_offset` from the previous response when `has_more=true`.
- Note: `all_pages` was removed upstream — it issued up to 30 upstream requests per billed call and omitted `has_more` / `next_offset`, so callers could not tell the result was tru

- Tool ID: `tikhub/wechat-mp-v2-fetch-comment-replies`
- Name in the catalog: Wechat_mp, Get WeChat MP Comment Replies
- Provider: [TikHub](/providers/tikhub.md)
- Capability: [WeChat comments](/tools/wechat/comments.md)
- Price: $0.01 per call
- Authentication: an authorised Agentik workspace is required for execution, including zero-price tools.

## Pricing contract

The provider’s price, with no markup. Billed for measured usage.


```json
{
  "model": "per_call",
  "amountUsd": 0.01
}
```

Pricing source: [https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info](https://api.tikhub.io/api/v1/tikhub/user/get_all_endpoints_info). Official per-success route price USD 0.01; daily upstream discounts may reduce provider cost. No discount invented for the customer. 10/second.

Price verification date: 2026-10-05.

## Complete input schema


```json
{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "pattern": "^https?://mp\\.weixin\\.qq\\.com/s([/?].+)?$",
      "title": "Url",
      "description": "公众号文章链接（https://mp.weixin.qq.com/s/…）/WeChat MP article URL (https://mp.weixin.qq.com/s/…)"
    },
    "content_id": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 32,
          "pattern": "^[0-9]*$"
        },
        {
          "type": "null"
        }
      ],
      "title": "Content Id",
      "description": "目标一级评论的 content_id（纯数字），不传则自动取第一条有回复的评论/content_id (numeric) of the target first-level comment; defaults to the first comment that has replies",
      "default": ""
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "title": "Offset",
      "description": "回复翻页偏移，首页 0；has_more=true 时传上次返回的 next_offset/Reply pagination offset, 0 for first page; pass next_offset from the previous response when has_more=true",
      "default": 0
    },
    "comment_id": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 32,
          "pattern": "^[0-9]*$"
        },
        {
          "type": "null"
        }
      ],
      "title": "Comment Id",
      "description": "文章的评论 id（可选，**性能捷径**）：不传时上游要先抓并解析整篇文章 HTML 才能拿到它，约占本接口耗时的一半；已有该值时传进来可显著加快。取自 /fetch_article_detail 或 /fetch_article_detail_h5 响应的 `$.data.content.comment_id`/Article comment id (optional, performance shortcut): when omitted, upstream must fetch and parse the whole article HTML to obtain it, which accounts for about half of this endpoint's latency"
    },
    "raw": {
      "type": "boolean",
      "title": "Raw",
      "description": "True=原始响应；False=精简解析结构/True=raw response; False=simplified parsed structure",
      "default": true
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}
```

## Published example

This is the provider tool’s published example. Replace example values with the user’s requested inputs, respecting the schema; do not execute an example merely to test a connection.


```json
{
  "tool_id": "tikhub/wechat-mp-v2-fetch-comment-replies",
  "input": {
    "url": "http://mp.weixin.qq.com/s?__biz=Mzk3NTA0MzM5NA==&mid=2247483745&idx=1&sn=3f34e768cf457a501038991ed30be1f4#rd",
    "content_id": "12109128638545265979",
    "offset": 0,
    "raw": true
  }
}
```

## Execute and retrieve

Inspect again before execution, explain the price and obtain the required authority. Use MCP run_tool or POST /v1/run with this tool ID, valid input and an idempotency key. Save the returned run ID and follow the actual state. If Agentik answers that the tool is temporarily unavailable, do not retry it blindly; use discovery to propose an alternative.

A partial or uncertain result can still have consumed provider resources. Consult [billing](/docs/billing.md), [idempotency](/docs/idempotency.md) and [asynchronous results](/docs/async.md).

[Provider documentation](https://api.tikhub.io/#/WeChat-Media-Platform-V2-API/fetch_comment_replies_api_v1_wechat_mp_v2_fetch_comment_replies_post)

[REST inspection](https://api.agentik.cc/v1/tools/tikhub/wechat-mp-v2-fetch-comment-replies) · [OpenAPI](/openapi.json) · [Connection guide](/connect.md)

---

[HTML page](/providers/tikhub/wechat-mp-v2-fetch-comment-replies) · [Agent index](/llms.txt)