Skip to main content
Glama

SocialDataX YouTube MCP

youtube_get_channel_info_by_url

Read-only

根据 YouTube 频道主页链接获取频道资料。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_urlYesYouTube 频道主页链接;支持 https://www.youtube.com/@用户名、/channel/、/c/ 和 /user/ 链接形态。如果传入频道 tab 子页链接,会规范化到对应的 https://www.youtube.com/... 频道主页。从搜索、详情、评论或评论回复结果读取频道资料时,直接传 author.profile_url;不要传 channel_id、裸 @用户名、频道名称、视频链接、播放列表链接或搜索页链接。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioYes频道简介;不可用时为空字符串。
nameYes频道名称;不可用时为空字符串。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
countryYes频道公开国家或地区;不可用时为空字符串。
verifiedYes频道是否有认证标识。
avatar_urlYes频道头像链接;不可用时为 null。
banner_urlYes频道横幅图链接;不可用时为 null。
channel_idYesYouTube 频道 ID;用于识别和去重。
view_countYes频道累计观看次数;不可用时为 null。
profile_urlYes频道主页链接;不可用时为 null。
external_linksYes频道主页外链列表;无外链时为空数组。
follower_countYes订阅者数量;可能为近似值;不可用时为 null。
posted_video_countYes频道视频数量;不可用时为 null。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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. The description adds useful behavioral detail beyond that, including supported URL forms (/@, /channel/, /c/, /user/) and normalization of tab subpage links to the channel homepage. No contradictions with annotations were found.

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 tool description is a single focused sentence that states the core purpose, and all supporting detail is appropriately placed in the parameter documentation. There is no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only tool with an output schema and clear annotations, the definition is complete. The parameter documentation covers edge cases like tab subpage links and invalid inputs, so an agent has everything needed to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the parameter description still adds substantial meaning beyond the schema: it enumerates accepted URL shapes, explains normalization behavior, identifies the proper source field (author.profile_url), and explicitly lists rejected input types. This is excellent guidance for correct invocation.

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 action ('获取频道资料' / get channel info) and the specific input resource (YouTube channel homepage URL). It distinguishes itself from siblings like youtube_get_user_posted_videos_by_channel_url by focusing on channel profile data, though it does not explicitly name or contrast any sibling tool.

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

Usage Guidelines4/5

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

The parameter description provides strong usage context: pass author.profile_url from search/detail/comment results, and avoid channel_id, bare @usernames, channel names, video links, playlist links, or search page links. However, it does not explicitly discuss when to choose this tool over the sibling video-focused tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources