Skip to main content
Glama

SocialDataX 微博 Weibo MCP

weibo_get_user_info_by_profile_url

Read-only

根据微博用户主页链接获取用户资料。

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": {
      "profile_url": "<profile_url>"
    },
    "name": "weibo_get_user_info_by_profile_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_urlYes微博用户主页链接;请传用户主页链接,不要传帖子链接、昵称或 user_id。

Output Schema

NameRequiredDescriptionDefault
bioYes用户简介;不可用时为空字符串。
nameYes用户名称;不可用时为空字符串。
pointsYes本次成功调用的积分消耗与账户积分余额。
user_idYes微博用户 user_id,可作为用户资料或用户帖子列表工具输入。
verifiedYes是否为认证账号。
avatar_urlYes用户头像链接;不可用时为 null。
post_countYes已发布微博数;不可用时为 null。
profile_urlYes微博用户主页链接;可用于打开用户主页;不可用时为 null;需要继续查询用户资料或用户帖子列表时优先使用非空 user_id。
follower_countYes粉丝数;不可用时为 null。
following_countYes关注数;不可用时为 null。
verification_labelYes认证说明;不可用时为 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. Changed11 schema fields changed
    • 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 / name / title
      Added value: +"Name"
    • addedOutput schema / properties / post_count / title
      Added value: +"Post Count"
    • addedOutput schema / properties / profile_url / title
      Added value: +"Profile Url"
    • 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: +"WeiboUserInfoData"
  4. Changed3 schema fields changed
    • addedOutput schema / properties / verification_label
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "认证说明;不可用时为 null。"
      +}
    • removedOutput schema / properties / verified_reason
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "description": "认证说明;不可用时为 null。"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "user_id",
      -  "name",
      -  "avatar_url",
      -  "profile_url",
      -  "bio",
      -  "follower_count",
      -  "following_count",
      -  "post_count",
      -  "verified",
      -  "verified_reason",
      -  "points"
      -]New value: +[
      +  "user_id",
      +  "name",
      +  "avatar_url",
      +  "profile_url",
      +  "bio",
      +  "follower_count",
      +  "following_count",
      +  "post_count",
      +  "verified",
      +  "verification_label",
      +  "points"
      +]
  5. Changed2 schema fields changed
    • addedOutput schema / properties / points
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
      +  "properties": {
      +    "balance": {
      +      "description": "本次接口完成时看到的当前积分余额。",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "cost": {
      +      "description": "本次请求最终确认消耗的积分。",
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "cost",
      +    "balance"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "user_id",
      -  "name",
      -  "avatar_url",
      -  "profile_url",
      -  "bio",
      -  "follower_count",
      -  "following_count",
      -  "post_count",
      -  "verified",
      -  "verified_reason"
      -]New value: +[
      +  "user_id",
      +  "name",
      +  "avatar_url",
      +  "profile_url",
      +  "bio",
      +  "follower_count",
      +  "following_count",
      +  "post_count",
      +  "verified",
      +  "verified_reason",
      +  "points"
      +]
  6. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and an output schema documents the return shape, so the description's burden is light. Nevertheless it adds no behavioral context at all, such as failure modes for invalid or private profiles or what the fetched profile contains, so it contributes nothing beyond the structured fields.

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, front-loaded sentence with no wasted wording, well matched to a one-parameter lookup tool. It is efficient, though its brevity comes at the cost of any usable guidance.

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?

For a simple one-parameter read tool with full schema coverage, annotations, and an output schema, the definition is adequate but minimal. Nothing critical is missing given the rich structured fields, yet the description itself would not help an agent decide between it and the by_user_id sibling.

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's parameter description already spells out the negative cases (no post link, no nickname, no user_id). The description only restates that a profile URL is required, adding nothing beyond the schema, so the baseline 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 ('获取用户资料' from a '微博用户主页链接'), which lets an agent distinguish it from post-oriented siblings. It does not, however, explicitly contrast itself with the sibling weibo_get_user_info_by_user_id; that distinction is only carried by the tool name and schema.

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 implied: an agent holding a profile URL will pick this tool, and the schema's warning against post links, nicknames, and user_id narrows it further. Still, the description itself gives no explicit when-to-use or when-to-prefer-by_user_id guidance, so the routing is left to inference.

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