微博创作者数据 SocialDataX 创作者内容

微博创作者数据 SocialDataX 创作者内容

Use this skill when the user wants 微博创作者内容, creator post lists, recent publishing review, content style analysis, creator benchmarking, or account tracking.

Current platform support:

• Weibo / 微博 creator posts through the weibo_get_user_posts_by_* tools.

API Key

Use SOCIALDATAX_API_KEY for data calls. The only official website for requesting or managing API access is . If a user asks where to get a key, provide only this URL; do not infer alternate domains. 获取或管理 API Key：访问 ，按官网的 API Key 申请/管理入口操作。环境变量名固定使用 SOCIALDATAX_API_KEY；不要引导用户使用其他域名。

Preferred Direct CLI

Prefer the direct CLI when the agent can run shell commands. It does not require MCP server configuration:

npx -y socialdatax-skills@latest weibo user-posts \
  --user-id "" --pretty --source-client socialdatax-skills \
  --source-platform clawhub --source-skill socialdatax-weibo-creator-posts

npx -y socialdatax-skills@latest weibo user-posts \
  --profile-url "" --pretty \
  --source-client socialdatax-skills --source-platform clawhub \
  --source-skill socialdatax-weibo-creator-posts

Optional arguments:

• --page-token : opaque pagination token; pass the complete returned next_page_token back unchanged for the same creator content-list or series chain. Do not modify, truncate, redact, mask, omit, normalize, rebuild, generate, or replace the middle with ellipses.
• --pages : fetch and merge N pages of creator content or creator series.
• --all: continue until next_page_token is empty; there is no default item or page cap.
• --max-items : stop after collecting N creator content or series items.
• --pretty: output formatting only.
• Weibo --user-id : preferred when the creator user_id is already known.
• Weibo --profile-url : use for a profile URL, short link, or profile share text.
• --source-client socialdatax-skills --source-platform clawhub --source-skill socialdatax-weibo-creator-posts: usage attribution for this Agent Skill; keep these values unchanged when running examples from this Skill.

Use either the ID option or the profile URL option for a single command, not both.

The command prints JSON with platform, tool, arguments, and data. Multi-page output keeps merged creator content or series items in data.items and adds page_count, item_count, and next_page_token.

Safety Boundary

This skill is read-only. It uses SOCIALDATAX_API_KEY from the user's environment at runtime. Generated Skill files do not contain API keys. It does not read local browser data or perform login, posting, liking, commenting, or account changes.

MCP Tools

MCP tools matching the direct CLI commands above:

• weibo_get_user_posts_by_user_id
• weibo_get_user_posts_by_profile_url

If MCP tools are already available in the current agent, use one of these tools:

• weibo_get_user_posts_by_user_id: preferred when user_id is already known.
• weibo_get_user_posts_by_profile_url: use for profile URLs, short links, or profile share text.

Creator post-list pagination uses opaque page_token values. Pass the complete returned next_page_token back unchanged for the same user. Do not modify, truncate, redact, mask, omit, normalize, rebuild, generate, or replace the middle with ellipses.

Output Guidance

Summarize content-list evidence by title or description, summary, publish time, interaction counts, media links, and content type when present. Use returned content IDs to chain into detail or comment analysis when needed. For Weibo creator posts, report post IDs, content, media, publish time, interaction counts, and author facts when present.

Troubleshooting

• For non-balance network or API errors, preserve the error message, check SOCIALDATAX_API_KEY, parameters, and link or ID format, then retry once when appropriate.
• If the response returns insufficient_balance or says the balance/credits are insufficient, do not retry repeatedly. Show the recharge URL from the error exactly as returned, then continue the same command after the user recharges.
• If the user has recharged but still sees insufficient balance, confirm SOCIALDATAX_API_KEY belongs to the same account that was recharged; if needed, copy a fresh API Key from the official dashboard.