SocialDataX 今日头条 MCP

toutiao_get_user_info_by_user_id

Read-only

读取头条用户资料和主页统计，缩略统计为近似值；已有数字用户 ID 时优先使用本工具，只有主页链接时使用 toutiao_get_user_info_by_profile_url。

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": {
      "user_id": "<user_id>"
    },
    "name": "toutiao_get_user_info_by_user_id"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes	头条数字用户 ID，可取搜索或详情的 author.user_id；不要传内容 ID、主页链接或主页标识。

Output Schema

Name	Required	Description
`bio`	Yes	用户简介；未填写时为空字符串。
`name`	Yes	用户显示名称。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`user_id`	Yes	数字用户 ID，可用于查询用户资料。
`verified`	Yes	用户是否已认证。
`avatar_url`	Yes	用户头像链接；未提供时为 null。
`ip_location`	Yes	主页显示的 IP 属地；未提供时为空字符串。
`profile_url`	Yes	用户主页链接，可用于再次查询用户资料。
`follower_count`	Yes	粉丝数；头条使用万等缩略显示时为换算的近似值。
`following_count`	Yes	关注数；头条使用万等缩略显示时为换算的近似值。
`verification_label`	Yes	认证说明；无认证说明时为空字符串。
`received_like_count`	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
```
Changed12 schema fields changedNov 3, 2026
- addedOutput schema / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / bio / title
```
Added value: +"Bio"
```
- addedOutput schema / properties / follower_count / title
```
Added value: +"Follower Count"
```
- addedOutput schema / properties / following_count / title
```
Added value: +"Following Count"
```
- addedOutput schema / properties / ip_location / title
```
Added value: +"Ip Location"
```
- addedOutput schema / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / received_like_count / title
```
Added value: +"Received Like Count"
```
- addedOutput schema / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / verification_label / title
```
Added value: +"Verification Label"
```
- addedOutput schema / properties / verified / title
```
Added value: +"Verified"
```
- addedOutput schema / title
```
Added value: +"ToutiaoUserInfoResult"
```
First observedOct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds a genuine data-quality caveat that abbreviated statistics are approximate values, which an agent needs in order to present results honestly. It stops short of describing pagination or return shape, though an output schema exists to carry that load.

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 semicolon-delimited sentence that front-loads the purpose, then the accuracy caveat, then the routing rule. Every clause earns its place, though the density makes it slightly harder to scan than a two-sentence split would be.

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?

For a one-parameter read-only lookup with full schema coverage and an output schema, the description supplies purpose, accuracy caveat, and sibling routing — enough to call it correctly. Only marginal items such as auth prerequisites or rate limits are absent.

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 the schema itself already warns against passing content IDs, homepage links, or homepage identifiers, so the description's only parameter contribution is the implicit condition that a numeric ID must already be known. That is a reasonable baseline 3 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?

States a specific verb and resource (读取头条用户资料和主页统计) and immediately contrasts itself with the sibling that handles the URL-based lookup case. An agent can distinguish it from toutiao_get_user_info_by_profile_url 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?

Gives an explicit selection rule: use this tool when a numeric user ID is already in hand, and switch to toutiao_get_user_info_by_profile_url when only a homepage link exists. Both the when and the alternative are named outright.

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?