Skip to main content
Glama

SocialDataX 微博 Weibo MCP

weibo_search_users

Read-only

按关键词搜索微博用户,返回用户标识、名称、头像、主页、粉丝数和认证说明。查找帖子使用帖子搜索;已有 user_id 或主页链接时使用用户详情工具。支持 page_token 翻页,各页结果可能重复;是否结束以 next_page_token 为空为准。

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_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes用户搜索词,例如 美食、月半美食记;不要传链接、用户 ID 或分页令牌。
page_tokenNo首次留空;续页原样传入上一页的 next_page_token,并保持 keyword 不变。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页用户列表,保持搜索结果顺序。
pointsYes本次成功调用的积分消耗与账户积分余额。
next_page_tokenYes下一页令牌;为空表示结束,非空时可原样传回继续翻页。

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. Changed10 schema fields changed
    • addedOutput schema / properties / items / items / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / items / items / properties / follower_count / title
      Added value: +"Follower Count"
    • 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 / title
      Added value: +"WeiboSearchUserItem"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / title
      Added value: +"WeiboSearchUsersResult"
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, the description discloses a genuinely non-obvious behavior: results may repeat across pages, and termination is signaled by an empty next_page_token rather than by a page count. It does not mention page size, rate limits, or auth requirements, so it stops short of full disclosure.

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?

Three dense sentences ordered as purpose, alternatives, then paging caveat — the disambiguation arrives before the operational detail. No filler, and the pagination warning is placed where an agent will read it before calling.

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?

With an output schema present, the description does not need to explain return shape, yet it still lists fields briefly — harmless but partly redundant. Everything needed to call correctly and to page safely is present; only per-page result counts are unstated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema lacks: that page_token paging can yield duplicate items and that the loop ends when next_page_token is empty. The keyword semantics themselves are left entirely to the schema.

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?

The description states a specific verb and resource ('按关键词搜索微博用户') and enumerates the returned fields, so the agent knows exactly what the tool produces. It also explicitly names what it is not by pointing to post search and the user-detail tools, which separates it cleanly from weibo_search_posts and weibo_get_user_info_by_user_id.

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?

It gives both exclusions and routing: use post search for posts, and use the user-detail tool when a user_id or profile URL is already known. Those conditions cover the main ambiguity an agent would face with this sibling set.

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