Skip to main content
Glama
if530770

redfox-mcp-server

by if530770

weibo-realtime-search

Search Weibo posts in real time by keyword to track public discussions and monitor social sentiment across result pages.

Instructions

微博实时搜索,按关键词实时搜索微博内容

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo页码
keywordYes搜索关键词

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.4

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It reveals that the search is real-time and keyword-based, but it does not disclose pagination behavior, result format, freshness limitations, or whether the operation is read-only. That is too little context for a tool with no annotation support.

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?

The description is short and easy to scan, with no unnecessary elaboration. There is minor redundancy in repeating '实时搜索', but overall it is appropriately concise.

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 two-parameter tool with no output schema, the description plus schema is minimally sufficient for invocation. However, the lack of annotations and the absence of differentiation from similar Weibo search tools makes the definition incomplete for confident tool selection.

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%, so the keyword and page parameters are already documented. The description adds only the 'real-time' framing and no additional semantic detail about how the parameters behave or interact.

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 clearly states the operation: search Weibo content in real time by keyword. It is specific enough to understand the core action, but it does not distinguish itself from sibling tools like weibo-post-search or weibo-hot-search, as '微博内容' is broad.

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?

The intended use is implied: use this tool when you need real-time keyword-based Weibo search. However, there is no explicit when-to-use versus when-not-to-use guidance, and no alternative tools are mentioned, leaving sibling differentiation to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/if530770/redfox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server