Ayrshare

@Ayrshare show me the last 10 posts we published across all platforms, including engagement metrics for each one.

Retrieved 10 recent posts from your Ayrshare history. The most recent post (LinkedIn, published 2 days ago) received 47 likes and 3 comments. Your Twitter thread from last week got 12 retweets and 89 likes. Instagram carousel from 5 days ago shows 203 likes, 18 comments. The data includes post IDs, platforms, timestamps, and engagement counts for each entry. Note that metrics refresh on different schedules per platform—LinkedIn and Twitter update hourly, Instagram every 6 hours.

This example demonstrates the read capability for post history and metrics. Requires API key with read permissions. Engagement data lags behind real-time by platform-specific intervals. The MCP returns structured data that the AI can summarize or compare across time periods.

@Ayrshare delete the post with ID 'ayr_post_12345' that we scheduled for tomorrow—we're pivoting the campaign direction.

Successfully deleted post ID 'ayr_post_12345' from your Ayrshare schedule. This post was queued for LinkedIn and Twitter, scheduled for tomorrow at 10:00 AM EST. The content has been removed from both platforms' queues. Note: if this were a published Instagram or TikTok post, deletion would not be possible due to platform API restrictions—only scheduled posts can be removed from those networks.

This write-action example shows the deletion tool in practice. Critical limitation: Instagram and TikTok published posts cannot be deleted via API, only scheduled ones. Always verify the post ID before deletion—there's no undo. Requires API key with write permissions. Use this when campaign priorities shift or content needs last-minute changes.

@Ayrshare set up an auto-schedule to post every weekday at 9 AM and 3 PM EST, skipping weekends entirely.

Created a new auto-post schedule in Ayrshare with two daily time slots: 09:00 and 15:00 EST, active Monday through Friday only. This schedule will now govern when queued posts go live across your connected platforms. Any posts added to your Ayrshare queue without explicit timestamps will automatically publish at the next available slot in this pattern. You can modify or delete this schedule later if posting cadence needs adjustment.

This synthesis example pairs the MCP's scheduling tool with strategic planning. The auto-schedule feature is powerful but requires understanding the queue model—posts without explicit times inherit the schedule. Weekday filtering is optional; omitting it posts 7 days a week. Requires API key with schedule-management permissions. Useful for teams maintaining consistent posting rhythms without manual timestamp entry.

When Ayrshare fits solo consultants posting 3-5x per week

A solo consultant or 2-person agency posting LinkedIn updates three times a week can use Ayrshare's auto-schedule tools to batch-write content on Mondays and let the MCP handle the rest. The four-tool scope is narrow—create schedule, set times, pull history, delete posts—but that's enough if your workflow is "write five posts, queue them for Tuesday/Thursday/Saturday at 9am, check metrics Friday". The API key auth means anyone on the team can run the same prompts without OAuth friction. This breaks down when you need platform-specific previews, A/B testing, or approval workflows; Ayrshare doesn't surface those levers in the MCP. If you're posting daily or managing clients across six platforms, you'll hit the tool ceiling fast. For the consultant posting a few times a week to one or two channels, it's a clean fit.

Using post history to audit what actually shipped

A three-person growth team running a product launch wants to pull every post published in the last 30 days and compare planned vs. actual timing. The "Get Post History" tool filters by date range and status, so you can ask the MCP "show me all posts that went live between March 1 and March 15" and get metrics in one query. This is faster than logging into Ayrshare's dashboard if you're already working in Switchy and want to paste the output into a retro doc. The limit: you can't edit posts or reschedule them through the MCP, only view and delete. If your retro uncovers a mistake, you'll delete the bad post via MCP and recreate it manually. That's fine for a monthly audit; it's clunky if you're doing daily QA. Use this when you need read-heavy reporting, not real-time campaign management.

When bulk deletion saves time after a fundraiser ends

A four-person nonprofit team promoted a fundraising event with 12 scheduled posts across Facebook, LinkedIn, and Twitter. The event ended early, and now they need to cancel the remaining posts before they go live. The "Delete a previously published Ayrshare post" tool lets you remove posts by ID, so you can ask the MCP "delete all scheduled posts with 'fundraiser' in the title" if you've already pulled the history. The catch: Instagram and TikTok posts can't be deleted once published, per Ayrshare's API limits, so this only works for pre-publish cleanup or platforms that allow retroactive deletion. If your event calendar changes weekly and you're constantly rescheduling, the lack of an "edit post" tool will frustrate you. For the nonprofit that runs three big campaigns a year and needs fast teardown after each, it's a time-saver.