Run any Skill in Manus with one click

messages

Stars17

Forks2

UpdatedJune 5, 2026 at 19:23

Direct messages (DMs) for the Ayrshare MCP server: read conversations and messages, send a DM, and manage the account's DM auto-responder. Use whenever someone wants private/direct messages on Facebook, Instagram, or Twitter/X: "read my Instagram DMs", "show our Facebook conversations", "what messages came in on X", "reply to that DM", "send a direct message", "DM them this link/photo", "answer the latest message". Also for auto-reply settings: "set up an auto-reply for DMs", "turn on the DM auto-responder", "change the auto-reply message", "what is our auto-responder set to", "turn off auto-replies". Trigger when calling `mcp__ayrshare__get_messages`, `mcp__ayrshare__send_message`, `mcp__ayrshare__get_auto_response`, or `mcp__ayrshare__set_auto_response`, and even without "Ayrshare": if the user wants to read or send social DMs, or configure a DM auto-reply, through an AI assistant, this is the skill. DMs exist ONLY on Facebook, Instagram, and Twitter/X.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ayrshare

ayrshare/ayrshare-social-media-api-claude-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

More from this repository

same repository

errors

ayrshare/ayrshare-social-media-api-claude-plugin

Error explanation for the Ayrshare MCP server: translate an Ayrshare error code into a plain-English cause, a classification, and a fix. Use whenever a code or numeric error needs decoding: "what does Ayrshare error 156 mean", "why did that post fail with code 272", "explain this error", "what is error code 110 on Instagram", "how do I fix this Ayrshare error". Trigger when calling `mcp__ayrshare__explain_error`, and even without the word "Ayrshare": if the user surfaces a social-posting error code and wants to know what it means or how to fix it, this is the skill. CRITICAL: whenever ANY OTHER Ayrshare MCP tool returns a structured error code (for example `Error 156: ...`), look the code up here and explain or fix it rather than echoing the raw error back. For the shared auth model and the global retry-safety rule, see `../getting-started/SKILL.md`.

2026-06-0617

draft-in-brand-voice

ayrshare/ayrshare-social-media-api-claude-plugin

Draft social posts that match a brand's established voice for the Ayrshare MCP server: first pull the profile's own past posts (history) to read tone, format, and what performed, then write platform-appropriate copy in that voice and validate it before anything publishes. Use whenever someone wants on-brand content rather than generic copy: "write a post the way we usually post", "draft this in our brand voice", "match our tone", "write like our LinkedIn", or any time content is created for a profile whose established style should be matched. Trigger even without the word "Ayrshare": if the user wants content that sounds like an existing account, this is the skill. It pulls history (`get_post_history` / `get_platform_history`), optionally `get_post_analytics` for what worked, drafts via `generate_post` or your own copy, then checks with `validate_post`. It produces DRAFTS only and never publishes; publishing is the explicit `create_post` step in `../post/SKILL.md`.

2026-06-0517

media

ayrshare/ayrshare-social-media-api-claude-plugin

Use whenever someone wants to confirm an image/video is usable for a social post, or asks to "upload", "resize", or "list" media, through the Ayrshare MCP server. The only media tool is `mcp__ayrshare__validate_media`, which HEAD-checks that a media URL is reachable (it does not upload, store, or resize anything). Trigger on phrasings like "upload this image so I can post it", "check that this video URL works before posting", "resize my image for Instagram", "make this fit a story", "what is in my media library", "is this picture going to be rejected", or any time a post needs an attachment and the media is not confirmed yet, even if the user never says "Ayrshare" or names a tool. Also trigger when a post failed because of a bad or unreachable media URL. IMPORTANT: the Ayrshare MCP has NO media upload, library, or resize tool; media is referenced by public URL and `validate_media` only HEAD-checks reachability. To attach a validated media URL to a post, see `../post/SKILL.md`.

2026-06-0517

plan-and-schedule-campaign

ayrshare/ayrshare-social-media-api-claude-plugin

Plan a multi-post, multi-platform social campaign and schedule it across networks via the Ayrshare MCP server: adapt copy and timing per platform, validate each post before it is scheduled, and confirm with the user before anything goes live. Use whenever someone wants more than one scheduled post: "plan a content calendar", "schedule a week of posts", "set up our product-launch sequence", "queue these announcements across LinkedIn and X", or any multi-post, multi-day, or multi-platform scheduling request. Trigger even without the word "Ayrshare": if the user wants a planned, scheduled run of posts rather than one immediate post, this is the skill. It orchestrates `validate_post` then `create_post` with a per-post `scheduleDate`, optionally `generate_post` / `recommend_hashtags` for drafting, and `get_post` / `update_post` to manage the queue. There is no bulk endpoint: a campaign is many individual scheduled posts, each validated and confirmed.

2026-06-0517

profiles

ayrshare/ayrshare-social-media-api-claude-plugin

Profile management for the Ayrshare MCP server: create profiles, list profiles, and generate social-account linking URLs for client/customer profiles under a Business account. Use whenever someone wants to onboard a new client, set up a customer's social accounts, "add a profile", "create a workspace for a client", list existing profiles, recover a lost `profileKey`, or get a link a client opens to connect their own social networks. Trigger when calling `mcp__ayrshare__create_profile`, `mcp__ayrshare__list_profiles`, or `mcp__ayrshare__generate_jwt_social_linking_url`, and even when the user does not say "Ayrshare": agency or white-label social setup, managing multiple clients' accounts through an AI assistant, or "send my client a link to link their socials". `generate_jwt_social_linking_url` mints the single sign-on URL the client opens to connect their networks, targeting the sub-profile from the `profileKey` argument or `Profile-Key` header (argument wins).

2026-06-0517

webhooks

ayrshare/ayrshare-social-media-api-claude-plugin

Webhook subscriptions for the Ayrshare MCP server: register, unregister, and list HTTPS push notifications so an agent or app is notified on events instead of polling. Use whenever someone wants event push: "notify me when a post publishes", "let me know when a scheduled post goes out", "set up a webhook for new comments", "send mentions to my endpoint", "list our webhooks", "what webhooks are registered", "stop sending webhooks for comments", "unsubscribe from the messages webhook". Trigger when calling `mcp__ayrshare__register_webhook`, `mcp__ayrshare__unregister_webhook`, or `mcp__ayrshare__list_webhooks`, and even without "Ayrshare": if the user wants push notifications for social-post or social-account events through an assistant, this is the skill. To confirm a queued post actually published, prefer the `scheduled` webhook over polling (then optionally `get_post` / `get_post_history`).

2026-06-0517

name

messages

description

Ayrshare MCP — Messages (DMs)

Four tools, split into two jobs — moving messages, and the account-level auto-responder:

mcp__ayrshare__get_messages — read conversations and messages for one platform. Its conversation/message ids feed send_message.
mcp__ayrshare__send_message — send a DM (text and/or media) to a recipient or into an existing conversation.
mcp__ayrshare__get_auto_response — read the account's DM auto-reply settings.
mcp__ayrshare__set_auto_response — change the account's DM auto-reply settings.

DMs are ONLY on Facebook, Instagram, and Twitter/X. No other network (LinkedIn, TikTok, YouTube, etc.) has a messaging surface here. get_messages and send_message are platform-scoped and accept exactly one of facebook, instagram, twitter. The two auto-response tools take no platform: they govern the selected profile's DM auto-reply across FB/IG/X at once (network-agnostic, but still scoped to the profile the profileKey argument or Profile-Key header selects).

All four are profile-scoped: choose the profile with the profileKey argument or the Profile-Key header (see Auth; the argument wins when both are set).

Functions

Tool	Purpose	Method + Endpoint	Required inputs	Optional inputs
`mcp__ayrshare__get_messages`	Read conversations / messages for one platform	`GET /messages/:platform`	`platform` (`facebook`\|`instagram`\|`twitter`)	`conversationsOnly` (bool), `conversationId`, `status` (`active`\|`archived`), `limit` (1-100, X/Twitter only), `next` (cursor, X only)
`mcp__ayrshare__send_message`	Send a DM (text and/or media)	`POST /messages/:platform`	`platform` (`facebook`\|`instagram`\|`twitter`); `message` OR `mediaUrls`; `recipientId` OR `conversationId`	— (none beyond the above)
`mcp__ayrshare__get_auto_response`	Read the account's DM auto-reply settings	`GET /messages/autoresponse`	— (no params)	—
`mcp__ayrshare__set_auto_response`	Update the account's DM auto-reply settings	`POST /messages/autoresponse`	at least one of `autoResponseActive` (bool), `autoResponseMessage` (string), `autoResponseWaitSeconds` (int)	— (none beyond the above)

Full input schemas and example payloads/responses are in references/schemas.md.

Auth

All four tools are profile-scoped: choose the profile with an optional profileKey tool argument or the Profile-Key connection header (the argument wins when both are set). Pass profileKey on the call to act as one client for that call, or set the Profile-Key header (.mcp.json headers) to default the whole connection to it; with neither, calls act on the account's primary/Business profile. Full model: ../getting-started/SKILL.md.

This applies to the auto-response tools too: they take no platform, but still act on whichever profile the profileKey argument or Profile-Key header selects. Different profiles → different DM auto-reply settings.

Usage guidance

Pick the platform first. get_messages and send_message are :/platform calls; pass exactly one of facebook, instagram, twitter. There is no "all platforms" mode — to scan three networks, make three calls.
Read before you reply. Call get_messages to pull conversations/messages, find the right conversation, then reply with send_message. Use conversationsOnly: true for a lightweight list of threads (no message bodies) when you just need to pick a conversation; drop it (or pass a conversationId) to read the messages within one thread.
send_message needs two things: content AND a target.
- Content: supply message (text), mediaUrls (an array of URLs), or both. At least one is required — an empty message with no media is rejected. On Twitter/X, message text is required even when you send mediaUrls — a media-only DM is rejected on X (FB/IG accept media-only). mediaUrls count also differs: Facebook and Instagram accept multiple URLs; X/Twitter accepts only one — sending more than one to X errors.
- Target: supply recipientId (the person/page-scoped user id) or conversationId (an existing thread). At least one is required.
Facebook and Instagram REQUIRE recipientId. On FB/IG you must address the message to a recipientId; a bare conversationId is not enough. On Twitter/X you can reply into a conversationId or send to a recipientId. When in doubt, include recipientId — it's the universally accepted target.
Where ids come from. recipientId and conversationId come out of get_messages. Read first to obtain them; don't guess or hand-construct ids.
Messaging windows are real. Each platform enforces a window in which you may DM a user; on Facebook/Instagram this follows Meta's standard messaging-window policy (tied to the user's last message to you). Outside the window the API returns a clear error. Don't retry it — translate it via mcp__ayrshare__explain_error and tell the user the window has closed (the customer must message first to reopen it). See the global retry rule in ../getting-started/SKILL.md.
limit and next are Twitter/X-only. limit (1-100) caps results and next is the pagination cursor — both apply to X only on get_messages. Don't pass them for Facebook or Instagram.
Auto-responder is account-level. get_auto_response takes no params and returns autoResponseActive, autoResponseMessage, autoResponseWaitSeconds. set_auto_response accepts any subset of those three; send the field(s) you're changing (at least one of the three is required). Sending autoResponseMessage: "" (empty string) resets the message to the Ayrshare default, it does not blank it out.

Gotchas

DMs are only FB / IG / X. get_messages and send_message reject any other platform. Don't try LinkedIn/TikTok/YouTube/etc. DMs through these tools — there is no messaging surface for them.
Be deliberate about scope. Whose DMs you read/send, and whose auto-responder you read/set, is set by the profileKey argument (per call; it wins) or the connection's Profile-Key header; with neither it's the primary profile. Confirm you're targeting the right profile before reading or sending.
send_message needs content AND target. Missing either side fails: you must give message OR mediaUrls, and recipientId OR conversationId. FB/IG additionally require recipientId specifically — a conversationId alone won't do. On Twitter/X, message text is required even with mediaUrls — a media-only DM (the generic "mediaUrls alone is fine" case) is rejected on X; it works only on FB/IG.
mediaUrls is an array of URLs. Media is referenced by reachable URL, same as posts — there is no upload step here. Validate a media URL with mcp__ayrshare__validate_media (see the Media skill) before sending if you're unsure it's reachable.
Auto-response empty string resets, not clears. autoResponseMessage: "" reverts to the Ayrshare default reply; it does not produce an empty auto-reply. To stop auto-replying entirely, set autoResponseActive: false.
Auto-response is not platform-scoped. get_auto_response/set_auto_response hit /messages/autoresponse with no platform; they govern the whole account's (profile's) DM auto-reply across FB/IG/X at once. Don't expect a per-platform toggle here.
On failure, call mcp__ayrshare__explain_error, then surface it — don't loop. send_message is a write: never auto-retry it on a 4xx. A closed messaging window, a bad/expired recipientId, or an unsupported platform won't fix itself on retry, and a blind resend can double-send. Translate the error via mcp__ayrshare__explain_error and present it; 429 gets at most one retry. (Mirrors the global retry-safety rule.)