Skip to main content
Glama

SocialDataX 微博 Weibo MCP

weibo_search_suggestions

Read-only

获取微博搜索框联想词,不返回帖子或用户详情,不支持分页;可将 text 用于帖子搜索,已有明确搜索词时可直接搜索帖子;已有帖子或用户主页链接时使用对应详情工具。

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_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. Changed4 schema fields changed
    • addedOutput schema / properties / items / items / properties / text / title
      Added value: +"Text"
    • addedOutput schema / properties / items / items / title
      Added value: +"WeiboSearchSuggestionItem"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / title
      Added value: +"WeiboSearchSuggestionsResult"
  4. Added

TDQS

A4.1/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 real context on top: results are suggestion strings only, no post or user detail payload is included, and pagination is unsupported. That pagination exclusion is exactly the kind of constraint an agent cannot learn from annotations, though nothing is said about result volume or rate limits.

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 front-loads the purpose and then stacks the constraints and routing rules in priority order. It is dense but each clause carries a distinct rule; only the run-on punctuation makes it slightly harder to scan than separate sentences would.

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?

An output schema exists, so return values need not be explained, and the description covers the remaining essentials: what is excluded, that paging is unavailable, and where to go next. The one gap is that it never clarifies what distinguishes these suggestions from user-name suggestions, which matters given the sibling list.

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?

With a single parameter at 100% schema coverage, the schema already explains that keyword is a term or phrase and warns against passing links, IDs, or pagination tokens. The description adds no further semantics for the input and instead references 'text', which appears to be a response field rather than a parameter.

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 names a specific verb and resource ('获取微博搜索框联想词') and immediately bounds the scope by stating it does not return posts or user details. That negative scoping lets an agent separate it from weibo_search_posts, weibo_search_users, and the detail tools without opening any schema.

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

Usage Guidelines4/5

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

It gives concrete routing rules: take the returned text and run a post search when you have a definite term, and switch to the corresponding detail tool when you already hold a post or profile link. It stops short of naming its closest sibling, weibo_search_user_suggestions, so the agent must infer which suggestion tool to pick when the target is a user.

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