SocialDataX 今日头条 MCP

toutiao_get_post_comment_replies_by_comment_id

Read-only

读取指定一级评论下的回复，按头条默认顺序分页；comment_id 取一级评论结果，续页保持该 ID，不要改用回复项自身的 ID。

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": {
      "comment_id": "<comment_id>"
    },
    "name": "toutiao_get_post_comment_replies_by_comment_id"
  }
}

Input Schema

Name	Required	Description	Default
`comment_id`	Yes	一级评论 ID，取一级评论结果的 comment_id；不要传内容 ID、链接或回复项自身的 comment_id。
`page_token`	No	首次留空；续页原样传入同一一级评论上一页回复结果的 next_page_token，并保持 comment_id 不变；不要使用一级评论或搜索的分页令牌。

Output Schema

Name	Required	Description
`items`	Yes	当前页评论回复列表。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`next_page_token`	Yes	下一页完整分页令牌；为空表示结束。

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```
Changed17 schema fields changedNov 3, 2026
- addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / items / items / properties / author / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / items / items / properties / author / title
```
Added value: +"ToutiaoCommentAuthor"
```
- addedOutput schema / properties / items / items / properties / comment_id / title
```
Added value: +"Comment Id"
```
- addedOutput schema / properties / items / items / properties / content / title
```
Added value: +"Content"
```
- addedOutput schema / properties / items / items / properties / image_urls / title
```
Added value: +"Image Urls"
```
- addedOutput schema / properties / items / items / properties / ip_location / title
```
Added value: +"Ip Location"
```
- addedOutput schema / properties / items / items / properties / like_count / title
```
Added value: +"Like Count"
```
- addedOutput schema / properties / items / items / properties / parent_comment_id / title
```
Added value: +"Parent Comment Id"
```
- addedOutput schema / properties / items / items / properties / publish_time / title
```
Added value: +"Publish Time"
```
- addedOutput schema / properties / items / items / properties / reply_to_comment_id / title
```
Added value: +"Reply To Comment Id"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"ToutiaoCommentReplyItem"
```
- addedOutput schema / properties / items / title
```
Added value: +"Items"
```
- addedOutput schema / properties / next_page_token / title
```
Added value: +"Next Page Token"
```
- addedOutput schema / title
```
Added value: +"ToutiaoCommentRepliesResult"
```
First observedOct 16, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar for what must be added is lower. The description adds useful operational detail beyond them: results come back in Toutiao's default order, and page continuation requires passing the prior next_page_token while keeping comment_id fixed.

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?

It is two compact, front-loaded sentences: first the purpose, then the paging constraint. Every clause is relevant, though the ID-consistency clause overlaps with what the schema descriptions already say.

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?

With only two parameters, full schema coverage, a declared output schema, and readOnly/openWorld annotations, the description supplies enough to invoke the tool correctly, including the main pagination pitfall. The only real gap is the lack of explicit routing guidance against siblings.

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 both parameters already carry detailed constraints, so the description only restates the comment_id scoping rule rather than adding new meaning. Under the high-coverage baseline, 3 is appropriate.

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 names a specific verb and resource, '读取指定一级评论下的回复', plus the ordering contract ('按头条默认顺序分页'). This clearly tells it apart from the sibling listing tools that operate on posts or URLs, but it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the input the description tells you to supply ('comment_id 取一级评论结果'), and it cautions against substituting the reply item's own ID. It stops short of an explicit when-to-use/when-not-to-use statement, such as saying to call toutiao_get_post_comments_by_post_id first to get the first-level comment IDs.

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

All SocialDataX 今日头条 MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?