Upload-Post

@Upload-Post list all profiles and show which social accounts are connected to each one

Found 3 Upload-Post profiles. Profile 'acme-marketing' (ID: prof_8x2k) is connected to Facebook Page 'Acme Corp' and LinkedIn organization 'Acme Inc.'; last auth refresh was 4 days ago. Profile 'personal-brand' (ID: prof_9m1z) is connected to Instagram account '@jane_doe' but shows a reauthentication warning—token expires in 2 days. Profile 'beta-test' (ID: prof_3n7p) has no connected platforms yet. All profiles are active and ready to accept posts once platforms are authenticated.

This example demonstrates the read-heavy List Profiles tool, which is the essential first step before publishing. Note that Upload-Post does not store your social-platform credentials—it uses OAuth tokens that expire. The output will flag reauthentication needs, so always check profile status before scheduling a campaign.

@Upload-Post enqueue a post to the acme-marketing profile: publish this photo to Facebook and LinkedIn tomorrow at 9am Pacific with caption 'New product launch'

Post enqueued successfully. Job ID: job_k4r8_scheduled. The photo has been staged and will publish to Facebook Page 'Acme Corp' and LinkedIn organization 'Acme Inc.' on 2025-06-15 at 09:00 Pacific (16:00 UTC). Caption: 'New product launch'. You can retrieve the upload status or cancel this job anytime before publication using the job ID. Note: LinkedIn may process the image asynchronously after publication; final post URL will be available within 2 minutes of the scheduled time.

This example shows the write-heavy Enqueue Post tool, which stages content for future publication. Upload-Post does not publish instantly—it schedules the post and returns a job ID. If you need to edit the caption or cancel, use the job ID with the appropriate tool. Be aware that each platform has rate limits; enqueueing 50 posts in one minute may trigger throttling.

@Upload-Post pull the last 30 days of post analytics for acme-marketing, then summarize which post type (photo vs text) got the most engagement on LinkedIn

Retrieved 47 posts from the last 30 days for profile 'acme-marketing'. LinkedIn data shows: 12 photo posts averaged 340 impressions and 18 reactions each; 8 text-only posts averaged 520 impressions and 31 reactions each. The text posts outperformed photos by 53% on impressions and 72% on reactions. Top-performing post was a text update on June 3rd (890 impressions, 54 reactions) discussing a product roadmap. Note: these are cached analytics; live platform data may differ slightly and would consume your LinkedIn API quota.

This synthesis example pairs the List Cached Post Analytics tool with the AI's reasoning to surface actionable insights. Upload-Post caches analytics to avoid hitting LinkedIn's strict rate limits on live requests. The cached data refreshes every 6 hours, so it's suitable for trend analysis but not real-time dashboards. Always verify critical metrics directly in the platform if precision matters.

When Upload-Post fits multi-client social scheduling

A 6-person agency managing 15 client social accounts needs a programmatic way to stage posts for approval before they go live. Upload-Post's Enqueue Post and List Scheduled Posts tools let you build a custom approval layer in Switchy: draft the post in a thread, call Enqueue with a future timestamp, then share the job ID with the client for sign-off. If they request changes, Cancel Scheduled Post wipes the staged assets and you re-enqueue. This works cleanly when each client has one or two profiles and you publish 10–30 posts per week. If you're scheduling hundreds of posts daily or need granular per-platform preview rendering, you'll hit the 12-tool ceiling fast and want a dedicated social-management platform instead. For small agencies where the bottleneck is client back-and-forth, not post volume, this MCP turns Switchy into a lightweight approval hub without paying for seats in Buffer or Hootsuite.

Coordinating one-time multi-network announcements

A 3-person startup is launching a feature and wants to hit LinkedIn, Facebook, Twitter, and Pinterest simultaneously at 9 AM Pacific. Upload-Post's List Platform Destinations confirms which networks are connected, then a single Enqueue Post call stages the identical text and image across all four. Get Upload Status polls for processing completion, and List Cached Post Analytics pulls engagement 24 hours later without burning API quotas on each platform. This scenario is ideal when you publish infrequently—maybe once a quarter—and don't want to log into four dashboards or remember four sets of credentials. If you're doing this weekly, the manual profile setup (Create Profile, then OAuth per network) becomes tedious and you'd rather use a native integration. For launch-day coordination where the team is already in Switchy discussing messaging, this MCP collapses four browser tabs into one AI call and keeps the post-mortem data in the same thread.

When Upload-Post isn't the right call for help content

A 5-person support team wants to auto-post new help articles to Twitter and LinkedIn when they publish in Notion. Upload-Post can technically enqueue the link and excerpt, but it has no webhook listener or Notion integration—you'd need to poll List Profiles, manually trigger Enqueue, and track which articles you've already posted. The 12-tool limit doesn't include content-source connectors, so you're building that glue yourself. If your help desk or CMS already has a Zapier or Make integration, those platforms handle the trigger logic better. Upload-Post wins when a human is in the loop deciding what to post and when; it's not designed for lights-out syndication. Use this MCP when your support lead is curating one weekly tip thread in Switchy and wants to cross-post the final version without leaving the workspace. For automated feed-to-social pipelines, stick with a dedicated automation tool.