WoopSocial

@WoopSocial list all draft posts in the 'Q1 Campaign' project and show me which social accounts each one targets

Found 4 draft posts in the Q1 Campaign project: 1. 'Spring Sale Announcement' → LinkedIn (Company Page), Twitter (@brand_official) 2. 'Product Teaser Video' → TikTok (@brandofficial), Instagram (@brand.official) — Note: TikTok delivery requires manual completion in-app 3. 'Customer Testimonial' → Facebook (Brand Page) 4. 'Behind-the-Scenes Photo' → Instagram (@brand.official), Twitter (@brand_official) All posts are in NOT_STARTED delivery state and can be edited or deleted. This is an illustrative summary; actual draft metadata includes media IDs, scheduling timestamps, and account-specific formatting.

This read-heavy example demonstrates WoopSocial's multi-platform draft management. Users should know that TikTok posts flagged MEDIA_UPLOAD require human intervention in the TikTok app before publication—WoopSocial cannot fully automate TikTok video uploads due to platform restrictions. The MCP requires API key auth with read access to projects and posts.

@WoopSocial create a new draft post with the text 'Excited to announce our new feature launch! 🚀' and schedule it for LinkedIn and Twitter tomorrow at 10 AM EST

Draft post created successfully (ID: pst_8x3k9m2n). • Text: 'Excited to announce our new feature launch! 🚀' • Targets: LinkedIn (Company Page), Twitter (@brand_official) • Scheduled: Tomorrow, 10:00 AM EST • Status: NOT_STARTED (delivery pending) The post is saved as a draft. To publish, you'll need to explicitly trigger publication or wait for the scheduled time. This example shows the typical creation flow; actual responses include full delivery metadata and any platform-specific validation warnings.

This write example shows WoopSocial's cross-platform scheduling. The MCP creates drafts but does not auto-publish unless explicitly instructed. Users must confirm their API key has write permissions for posts and that target social accounts are already connected in WoopSocial. Deletion is only possible while all deliveries remain NOT_STARTED—once a post begins publishing, it cannot be recalled via this MCP.

@WoopSocial review all posts published in the last 7 days across our social accounts and draft a performance summary highlighting which platforms got the most engagement

Analyzed 12 posts published across 4 social accounts in the past week: **Top Performer:** Instagram (@brand.official) — 3 posts, avg. 847 engagements/post (likes, comments, shares) **Second:** LinkedIn (Company Page) — 4 posts, avg. 312 engagements/post **Third:** Twitter (@brand_official) — 3 posts, avg. 189 engagements/post **Lowest:** Facebook (Brand Page) — 2 posts, avg. 94 engagements/post **Insight:** Video content on Instagram drove 2.3× more engagement than static images. Consider prioritizing Reels for Q2. This synthesis is illustrative; actual engagement metrics depend on WoopSocial's analytics integration with each platform's API.

This synthesis example pairs WoopSocial's post-retrieval tools with AI reasoning to surface actionable insights. The MCP can fetch historical post data, but engagement metrics depend on whether WoopSocial's API returns analytics—some platforms limit third-party access to performance data. Users should verify their social accounts grant analytics permissions and understand that rate limits may throttle bulk historical queries.

When draft-first posting saves client relationships

A 3-person social agency managing 8 client brands needs every post reviewed before it goes live. WoopSocial's Create Draft Post tool lets the team stage content in the client's project, send a Slack link for approval, then publish manually once the client signs off. The draft state prevents accidental publishing across TikTok, Instagram, and LinkedIn—critical when one rogue post can cost a contract. The 20-tool scope includes project and social-account management, so the team can onboard new clients and rotate credentials without leaving Switchy. If you're running approval gates with multiple stakeholders, this MCP keeps the guardrails tight.

How WoopSocial handles post deletion at scale

A startup managing 4 product sub-brands posts 60 times a week and needs to kill outdated campaigns fast when priorities shift. WoopSocial's Delete Post and Delete Social Account Post tools let the team purge scheduled content by exact ID—but only while deliveries are still NOT_STARTED. Once a post enters the publishing queue, deletion fails. This constraint works for teams that catch mistakes early in the workflow; it breaks down if you're trying to recall posts mid-flight. The media-cleanup tools (Delete Media) keep the library tidy after a campaign wraps. If your cadence is high and your review window is tight, this MCP fits.

When to wire WoopSocial events into your data stack

A 6-person growth team tracks social performance in a custom dashboard and needs real-time post-status updates without polling the API every minute. WoopSocial's webhook tooling (Delete Webhook implies Create/List exist) lets the team subscribe to publication events and pipe them into their analytics warehouse. The API-key auth means the integration runs in a shared Switchy context—no per-user OAuth dance. The trade-off: webhook management requires exact IDs and careful cleanup; if you delete a project or social account, you orphan the webhook and clutter your endpoint logs. If you're already running event-driven workflows and need social data in the loop, this MCP closes the gap.