Skip to main content
Glama

SocialDataX 微博 Weibo MCP

weibo_search_user_suggestions

Read-only

获取微博搜索框按关键词联想的少量用户候选,返回用户标识、名称、头像、主页、简介、粉丝数、认证信息、地区和是否正在直播。不支持分页,也不保证包含指定账号;需要翻页搜索用户时使用用户搜索,已有 user_id 或主页链接时使用用户详情。

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": {
      "keyword": "<keyword>"
    },
    "name": "weibo_search_user_suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes用户名称或关键词,例如 汽车之家、美食;不要传用户 ID、主页链接或分页令牌。

Output Schema

NameRequiredDescriptionDefault
itemsYes搜索框用户联想列表,保持返回顺序;没有候选时为空数组。
pointsYes本次成功调用的积分消耗与账户积分余额。

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. Changed13 schema fields changed
    • addedOutput schema / properties / items / items / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / items / items / properties / bio / title
      Added value: +"Bio"
    • addedOutput schema / properties / items / items / properties / follower_count / title
      Added value: +"Follower Count"
    • addedOutput schema / properties / items / items / properties / is_live / title
      Added value: +"Is Live"
    • addedOutput schema / properties / items / items / properties / location / title
      Added value: +"Location"
    • addedOutput schema / properties / items / items / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / items / items / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / items / items / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / items / items / properties / verification_label / title
      Added value: +"Verification Label"
    • addedOutput schema / properties / items / items / properties / verified / title
      Added value: +"Verified"
    • addedOutput schema / properties / items / items / title
      Added value: +"WeiboSearchUserSuggestionItem"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / title
      Added value: +"WeiboSearchUserSuggestionsResult"
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, and the description adds non-obvious behavior: no pagination support and no guarantee the requested account appears. It does not discuss rate limits or result ordering, keeping it shy of a 5.

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?

Purpose is front-loaded, followed by the field list and redirection to siblings; every clause carries information, though the return-field enumeration is somewhat dense in a single sentence.

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?

With one fully documented parameter, an output schema, and annotations covering safety, the description supplies everything needed: scope, limitations, and sibling routing.

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 itself warns against passing user IDs, profile links, or pagination tokens, so the description adds no parameter meaning beyond it. Baseline 3 applies.

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 (获取微博搜索框按关键词联想的用户候选) plus the returned fields, making it clearly distinct from weibo_search_users and the get_user_info_by_* siblings.

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?

Explicitly rules out pagination and names the alternatives with the condition that selects each: 需要翻页搜索用户时用用户搜索, 已有 user_id 或主页链接时用用户详情.

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