SocialDataX 今日头条 MCP

toutiao_get_post_comments_by_url

Read-only

通过头条内容链接或分享文案读取一级评论，按头条默认顺序返回，支持分页，不包含评论回复；只有内容 ID 时使用 toutiao_get_post_comments_by_post_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": {
      "url": "<url>"
    },
    "name": "toutiao_get_post_comments_by_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	头条内容链接或包含该链接的分享文案，支持 /article/ID/、/aID/、/video/ID/ 和 /w/ID/，可取搜索结果 post_url；不要传纯 ID。
`page_token`	No	首次留空；续页原样传入同一内容上一页评论结果的 next_page_token；不要使用搜索结果的分页令牌。

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
```
Changed16 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 / has_replies / title
```
Added value: +"Has Replies"
```
- 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 / publish_time / title
```
Added value: +"Publish Time"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"ToutiaoCommentItem"
```
- 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: +"ToutiaoCommentsResult"
```
First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds behavior beyond them: comments come back in the platform's default order, pagination is supported, and only first-level comments are returned. These are meaningful traits for planning retrieval. It does not discuss auth requirements, rate limits, or how deep pagination is bounded, which keeps it below a 5.

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?

It is one tight sentence: what it reads, how results are ordered, pagination support, what it excludes, then the alternative. The primary scope constraint is front-loaded and nothing is redundant.

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?

An output schema exists, so return values need not be explained, and the description still covers scope, ordering, pagination, and exclusion. For a two-parameter read tool with full schema coverage, that is nearly complete; only pagination depth or truncation behavior is left unstated.

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 coverage is 100%, and the schema already states accepted URL forms, the ban on pure IDs, and the page_token continuation rule. The description's mention of '内容链接或分享文案' mirrors what the url schema already documents, so it adds little new parameter meaning. A baseline 3 is appropriate when the schema does the heavy lifting.

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 specifies the verb and resource ('读取一级评论') along with the accepted input modalities ('内容链接或分享文案'), and it explicitly excludes a related resource ('不包含评论回复'). It names the sibling tool toutiao_get_post_comments_by_post_id for the ID-only case, so an agent can distinguish it from both the post_id variant and the replies tool without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit routing rule: use this tool when you have a link or share text, and use toutiao_get_post_comments_by_post_id when you only have a content ID. It also states the exclusion condition ('不包含评论回复'), which routes reply retrieval to toutiao_get_post_comment_replies_by_comment_id.

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?