360 Secure SkillHub
360 安全技能中心

WoopSocial

该 Skill 通过 WoopSocial 远程 MCP 服务完成社交媒体帖子发布:先列出项目与账号、按平台补充账号级选项、上传或复用媒体、校验内容,再创建帖子或定时发布,并区分待发、已排期、已发布与失败等交付状态。删除类操作需用户明确授权。

woopsocial
热度 11.74
最近更新 2026-07-14 21:22:12
分类:营销依赖:MCP 服务 / 第三方 API应用场景:社交媒体 / API 集成 / 日程安排 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add woopsocial
Metadata
name
woopsocial
description
Use WoopSocial's remote MCP server to publish and schedule social media posts, discover projects and connected accounts, upload media, validate content, inspect delivery status, and manage webhooks.

WoopSocial

Use WoopSocial MCP tools.

Connect

If WoopSocial tools are unavailable and the user wants to connect them, configure the remote MCP server with OAuth:

openclaw mcp add woopsocial \
  --url https://api.woopsocial.com/mcp \
  --transport streamable-http \
  --auth oauth

openclaw mcp login woopsocial
openclaw mcp doctor woopsocial --probe

Never print, store in the skill, or commit API keys or OAuth credentials. Follow the official integration guide at https://docs.woopsocial.com/mcp/integrating-clients when OAuth setup needs troubleshooting.

Posting Workflow

  1. Use projects_list to identify the project.
  2. Use social_accounts_list to resolve the requested accounts. All accounts for one post must belong to the same project.
  3. Use social_accounts_get_platform_inputs when a platform requires current account-specific options, such as a Pinterest board or TikTok privacy setting.
  4. Reuse existing media returned by media_list when appropriate. For new media, use the media_uploads_* session tools, upload every returned part exactly as instructed, complete the session, and wait until the media is ready.
  5. Build the post request from the user's content, accounts, platform-specific fields, and schedule. Use an explicit timezone or offset when interpreting a local time.
  6. Call posts_validate before posts_create. Resolve validation errors; surface material warnings to the user.
  7. Call posts_create only after the target accounts, content, and schedule are unambiguous.
  8. Return the post ID and requested schedule. For delivery results, use posts_get or social_account_posts_list and distinguish pending, scheduled, published, and failed states.

Action Boundaries

Treat an explicit request to publish or schedule as authorization for that action. Ask before creating the post only when its target accounts, content, schedule, or publish-versus-draft intent is ambiguous.

Require explicit user intent before calling delete tools for posts, account posts, projects, social accounts, media, or webhooks.

Never claim that a post was published merely because creation succeeded. Report the delivery state returned by WoopSocial.