Skip to main content
Glama

SocialDataX YouTube MCP

youtube_get_channel_info_by_url

Read-only

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

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": {
      "channel_url": "<channel_url>"
    },
    "name": "youtube_get_channel_info_by_url"
  }
}

Input Schema

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

Output 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. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed16 schema fields changed
    • addedOutput schema / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / banner_url / title
      Added value: +"Banner Url"
    • addedOutput schema / properties / bio / title
      Added value: +"Bio"
    • addedOutput schema / properties / channel_id / title
      Added value: +"Channel Id"
    • addedOutput schema / properties / country / title
      Added value: +"Country"
    • addedOutput schema / properties / external_links / items / properties / title / title
      Added value: +"Title"
    • addedOutput schema / properties / external_links / items / properties / url / title
      Added value: +"Url"
    • addedOutput schema / properties / external_links / items / title
      Added value: +"YoutubeChannelExternalLinkData"
    • addedOutput schema / properties / external_links / title
      Added value: +"External Links"
    • addedOutput schema / properties / follower_count / title
      Added value: +"Follower Count"
    • addedOutput schema / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / posted_video_count / title
      Added value: +"Posted Video Count"
    • addedOutput schema / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / verified / title
      Added value: +"Verified"
    • addedOutput schema / properties / view_count / title
      Added value: +"View Count"
    • addedOutput schema / title
      Added value: +"YoutubeChannelInfoData"
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds nothing about behavior: no detail on whether the call is rate-limited, what happens with a valid-looking but nonexistent URL, or whether the result is cached. For a network-facing read tool, it does not tell the agent anything beyond what the annotations already say.

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?

The definition is a single short sentence with no filler, and the purpose appears right at the start. It is concise to the point of being minimal, but nothing in it is wasted.

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

Completeness3/5

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

There is a single required parameter with a fully documented schema, and the output schema already covers the return value, so the description does not need to explain that. This tool has an easy job structurally, but it still does not mention where the tool sits among its many siblings, so it only meets the minimum.

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 the schema already documents the single channel_url parameter in detail, including URL forms, normalization behavior, and prohibited input types. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 states a specific verb and resource: fetch channel profile data from a YouTube channel homepage URL. That much is unambiguous. The only gap is that it does not distinguish this tool from siblings such as youtube_search_channels, which also returns channel-related data.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and never mentions alternatives. The input schema's channel_url description does give rich routing guidance about which URL forms to pass and which sources (author.profile_url) to read from, but the description itself could have pointed to that guidance.

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