Skip to main content
Glama

SocialDataX 微博 Weibo MCP

by com.52choujiang
OverviewDiscussionsAdmin

weibo_get_user_posts_by_profile_url

Read-only

根据微博用户主页链接获取用户帖子列表，支持 page_token 翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_tokenNo微博用户帖子列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一用户帖子列表分页链路，不能跨用户复用。
profile_urlYes微博用户主页链接；请传用户主页链接，不要传帖子链接、昵称或 user_id。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页微博用户帖子列表。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
next_page_tokenYes下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；next_page_token 只能用于同一能力和同一分页链路；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / images
      Added value: +{
+  "description": "图片列表，包含链接及宽高；无图时为空数组。",
+  "items": {
+    "properties": {
+      "height": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "图片高度，像素；不可用时为 null。"
+      },
+      "url": {
+        "description": "图片链接。",
+        "type": "string"
+      },
+      "width": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "图片宽度，像素；不可用时为 null。"
+      }
+    },
+    "required": [
+      "url",
+      "width",
+      "height"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "post_id",
-  "content",
-  "publish_time",
-  "post_url",
-  "like_count",
-  "comment_count",
-  "repost_count",
-  "play_count",
-  "image_urls",
-  "topic_tags",
-  "author"
-]New value: +[
+  "post_id",
+  "content",
+  "publish_time",
+  "post_url",
+  "like_count",
+  "comment_count",
+  "repost_count",
+  "play_count",
+  "image_urls",
+  "images",
+  "topic_tags",
+  "author"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / points
      Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "points"
+]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / topic_tags
      Added value: +{
+  "description": "微博帖子话题标签列表；无标签时为空数组。",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "description": "话题标签名称。",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "post_id",
-  "content",
-  "publish_time",
-  "post_url",
-  "like_count",
-  "comment_count",
-  "repost_count",
-  "play_count",
-  "image_urls",
-  "author"
-]New value: +[
+  "post_id",
+  "content",
+  "publish_time",
+  "post_url",
+  "like_count",
+  "comment_count",
+  "repost_count",
+  "play_count",
+  "image_urls",
+  "topic_tags",
+  "author"
+]
  4. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / play_count / description
      Previous value: -"播放数；不可用时为 null。"New value: +"帖子内视频播放数；没有视频或上游未返回时为 null，不是帖子浏览数。"
  5. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / play_count
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "播放数；不可用时为 null。"
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "post_id",
-  "content",
-  "publish_time",
-  "post_url",
-  "like_count",
-  "comment_count",
-  "repost_count",
-  "image_urls",
-  "author"
-]New value: +[
+  "post_id",
+  "content",
+  "publish_time",
+  "post_url",
+  "like_count",
+  "comment_count",
+  "repost_count",
+  "play_count",
+  "image_urls",
+  "author"
+]
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the read-only safety profile. The description adds that page_token pagination is supported, but detailed behavioral rules, such as opaque token handling and not reusing tokens across users, are in the schema description rather than the tool description. No contradiction with annotations is present.

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 one concise, front-loaded sentence stating the purpose and the key pagination capability, with no filler or redundant content. It is appropriately sized for a simple read-only list tool.

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 fully documented parameters and the presence of an output schema, the description does not need to explain return values or parameter details. It could be more complete by explicitly addressing when to use this tool rather than the user_id-based sibling, but the combination of description, schema, and annotations is largely sufficient.

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%, with both parameters richly documented: profile_url explains acceptable input and exclusions, and page_token fully specifies exact reuse rules and restrictions. The description itself does not add parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

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 action (get user posts list) and the input (Weibo profile URL), and mentions page_token pagination. It does not explicitly contrast with the sibling weibo_get_user_posts_by_user_id in the description text, though the tool name and profile_url field guidance ('do not pass user_id') reinforce differentiation.

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 profile_url parameter says to pass a user homepage link and not to pass post links, nicknames, or user_id, which implies the tool's intended input. However, there is no explicit statement of when to choose this tool over weibo_get_user_posts_by_user_id or other siblings; usage context is only implied by naming and input constraints.

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

All SocialDataX 微博 Weibo MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources