FeedMCP

Data APIs / Weibo

Weibo trending searches API

The top 50 Weibo trending searches right now: rank, heat and label, overall or by category.

Item Value
Endpoint GET https://api.feedmcp.com/v1/weibo/trends/list
ID weibo.trends.list
Price $0.002 / call
Returns A page of Trend objects
Auth Authorization: Bearer $FEEDMCP_API_KEY

The first item is pinned (rank 0); ad slots are removed.

Parameters

Name Type Required Description
category realtime / social / entertainment / tech / life / sports / games no Category: realtime, social, entertainment, tech, life, sports or games; default realtime

Every endpoint also takes view=full to include the platform's raw data as raw, at the same price.

Returned fields

data.items is a list of Trend objects, with the same fields on every platform:

Field Type Description
rank number Rank; 0 means pinned
platform string Platform
keyword string Term
heat number | null Heat (each platform counts its own way)
label string | null Label, such as pinned or hot
url string | null Search link on the platform

When you are charged

$0.002 per call that returns the list. An empty list (the platform did not answer), platform errors and timeouts are free; just retry.

Each answer carries meta.billing: what this call cost and the balance left.

Request

cURL

curl "https://api.feedmcp.com/v1/weibo/trends/list" \
  -H "Authorization: Bearer $FEEDMCP_API_KEY"

Python

import os, requests

r = requests.get(
    "https://api.feedmcp.com/v1/weibo/trends/list",
    params={},
    headers={"Authorization": f"Bearer {os.environ['FEEDMCP_API_KEY']}"},
    timeout=30,
)
print(r.json())

JavaScript

const res = await fetch("https://api.feedmcp.com/v1/weibo/trends/list", {
  headers: { Authorization: `Bearer ${process.env.FEEDMCP_API_KEY}` },
});
console.log(await res.json());

MCP

From an AI with FeedMCP installed, the call tool:

{
  "endpoint": "weibo.trends.list",
  "params": {},
  "max_price": "0.002"
}

Response

The data below is made up; the shape is the real one.

{
  "code": "ok",
  "request_id": "req_7Qm2kXb9TzLp",
  "data": {
    "items": [
      {
        "rank": 1,
        "platform": "weibo",
        "keyword": "初雪",
        "heat": 2345678,
        "label": "热",
        "url": "https://s.weibo.com/weibo?q=%23%E5%88%9D%E9%9B%AA%23"
      },
      {
        "rank": 2,
        "platform": "weibo",
        "keyword": "周末去哪儿",
        "heat": 1234567,
        "label": null,
        "url": "https://s.weibo.com/weibo?q=%23%E5%91%A8%E6%9C%AB%E5%8E%BB%E5%93%AA%E5%84%BF%23"
      }
    ]
  },
  "page": {
    "next_cursor": null,
    "has_more": false
  },
  "warnings": [],
  "meta": {
    "endpoint": "weibo.trends.list",
    "platform": "weibo",
    "fetched_at": "2026-11-19T08:00:00.000Z",
    "source": "FeedMCP",
    "catalog_revision": "d09a736bd39e8b3f",
    "billing": {
      "charged": true,
      "amount": "0.002",
      "currency": "USD",
      "balance": "9.98"
    }
  }
}

Errors are described in Errors: each says whether you were charged (charged) and whether to retry (retry).

Other Weibo endpoints

Questions

$0.002 per call that returns the list. An empty list (the platform did not answer), platform errors and timeouts are free; just retry.

Do I need a platform account?

No. Only public data is read.

A post ID is the number or code in a post link; a user ID is the number after /u/.

How do I get more items?

When the answer has page.next_cursor, pass it back as cursor for the next page. Each page is billed on its own.

How do I use it from an AI?

Install the MCP server and ask; your AI calls weibo.trends.list.