Weibo MCP Server

get_feeds

Retrieve a Weibo user's timeline content by providing their unique identifier, returning a list of feeds with configurable limits.

Instructions

Get a Weibo user's feeds
    
Returns:
    list[dict]: List of dictionaries containing feeds

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": {
      "uid": "<uid>"
    },
    "name": "get_feeds"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes	The unique identifier of the Weibo user
`limit`	No	Maximum number of feeds to return, defaults to 15

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 14, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool does and the return type, missing critical details like authentication requirements, rate limits, pagination behavior, or whether this is a read-only operation (though implied by 'Get').

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 very concise with only two sentences, front-loading the purpose and then specifying the return type. There's no wasted text, though it could be slightly more structured by integrating usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like authentication, error handling, or data format details, which are crucial for a tool that fetches user data from an external service like Weibo.

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?

The schema description coverage is 100%, so the parameters 'uid' and 'limit' are fully documented in the schema. The description adds no additional parameter semantics beyond what's in the schema, resulting in the baseline score of 3.

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 verb ('Get') and resource ('a Weibo user's feeds'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_hot_feeds' or 'search_content' that also retrieve feed-related data, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_hot_feeds' for trending content or 'search_content' for filtered searches, leaving the agent without context for tool selection.

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

Deploy Server