SocialDataX YouTube MCP

youtube_get_video_comments_by_url

Read-only

根据 YouTube 视频链接获取公开视频一级评论。

Input Schema

Name	Required	Description	Default
`sort_type`	No	评论排序方式：hot=热门评论，time_descending=较新评论优先。YouTube 可能保留作者评论或置顶评论在当前页前部；如无明确排序需求，保持 hot。	hot
`video_url`	Yes	YouTube 视频页面链接；支持 watch、youtu.be 短链和 Shorts 链接。从搜索结果读取评论时，直接传搜索结果里的 share_url（items[*].share_url）；不要传频道链接、播放列表链接、搜索页链接或裸 video_id。
`page_token`	No	YouTube 视频评论分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一视频和同一 sort_type 的评论续页；更换视频或 sort_type 时，请清空 page_token 后从第一页重新读取评论。

Output Schema

Name	Required	Description
`items`	Yes	当前页 YouTube 视频一级评论列表；当前页可能为空，是否可继续翻页以 next_page_token 是否为空为准。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`comment_count`	Yes	评论总数；不是当前页 items 数量；不可用时为 null。
`next_page_token`	Yes	下一页评论不透明分页令牌；为空表示没有更多评论。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；只用于当前 YouTube 视频和同一 sort_type 的评论续页；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。

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
```
Changed18 schema fields changedNov 3, 2026
- addedOutput schema / properties / comment_count / title
```
Added value: +"Comment Count"
```
- addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / channel_id / title
```
Added value: +"Channel Id"
```
- 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 / verified / title
```
Added value: +"Verified"
```
- addedOutput schema / properties / items / items / properties / author / title
```
Added value: +"YoutubeCommentAuthorData"
```
- 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 / is_author_comment / title
```
Added value: +"Is Author Comment"
```
- addedOutput schema / properties / items / items / properties / like_count / title
```
Added value: +"Like Count"
```
- addedOutput schema / properties / items / items / properties / publish_time_text / title
```
Added value: +"Publish Time Text"
```
- addedOutput schema / properties / items / items / properties / reply_count / title
```
Added value: +"Reply Count"
```
- addedOutput schema / properties / items / items / properties / reply_token / title
```
Added value: +"Reply Token"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"YoutubeCommentItemData"
```
- 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: +"YoutubeVideoCommentsResult"
```
First observedSep 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With readOnlyHint and openWorldHint already declared, the description still adds real value by scoping results to public, top-level comments (excluding replies and presumably hidden/private ones). It says nothing about pagination behavior in prose, quota consumption, or ordering caveats – those live only in the schema.

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?

A single well-formed sentence that front-loads the input source and the resource. Nothing is wasted, but the extreme brevity comes at the cost of under-specification rather than being a model of efficient density.

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 and parameters are exhaustively documented, so the description does not need to explain return values or token handling. What remains missing is sibling routing and any hint about comment volume or page size, but the definition is otherwise sufficient to call the tool correctly.

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%, so video_url, sort_type, and page_token are all fully documented in the schema with format rules and pagination constraints. The description adds no parameter-level meaning beyond what the schema already provides, which is the baseline case.

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 ('获取' + YouTube 视频一级评论) and constrains it to comments attached to a video link, which implicitly separates it from the replies sibling. However, it never names youtube_get_video_comment_replies or any other sibling, so the reader must infer the boundary from '一级评论' alone.

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 only implied: '根据 YouTube 视频链接' suggests the input is a page URL, and '一级评论' implies replies are out of scope. There is no statement of when to prefer this over youtube_get_video_comment_replies, no note on quota/cost relative to the submit tools, and no exclusions.

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

All SocialDataX YouTube 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?