cn-scraper-mcp

by goesByhc

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

weibo_user_timeline

Fetch recent posts from a Weibo user's timeline using their UID. Requires a SUB login cookie for authentication.

Instructions

获取微博用户时间线（最近发言）。

需要登录 cookie（SUB token）。可通过 weibo_search 找到目标用户获取其 UID。

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": "weibo_user_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes	用户 ID（数字，如 "2803301701" = 人民日报）
`limit`	No	返回帖子数 (默认 10)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 17, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions the need for authentication (cookie), which is critical, but does not discuss other aspects like rate limits, error handling, or whether the operation is read-only. The description is adequate but not comprehensive.

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?

The description is extremely concise: two sentences covering purpose, auth requirement, and auxiliary hint. No unnecessary words, and the most critical information is front-loaded.

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?

Given the tool has only two parameters and an existing output schema, the description covers the essential aspects: purpose, auth context, and parameter hints. It lacks details about output format or error behavior, but the output schema fills that gap. Fairly complete for a simple tool.

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?

Although schema coverage is 100%, the description adds value with a concrete example for the uid parameter (e.g., '2803301701' for People's Daily) and clarifies the default value for limit. This goes beyond what the schema provides.

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 clearly states the verb '获取' (get) and the resource '微博用户时间线' (Weibo user timeline), with the qualifier '最近发言' (recent posts). It is distinct from sibling tools like weibo_search or weibo_comments, which serve different purposes.

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?

The description explicitly mentions the prerequisite of a login cookie (SUB token) and provides guidance on how to obtain the required UID via weibo_search. This helps the agent decide when to use the tool, though it does not explicitly state when not to use it.

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