Webhooks
Skill ayrshare/ayrshare-social-media-api-claude-plugin/skills/webhooks
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`).From its SKILL.md
npx -y skills add ayrshare/ayrshare-social-media-api-claude-plugin --skill webhooksAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.6 KB, as published. Nobody here has run it
Ayrshare MCP — Webhooks
Three tools for subscribing your endpoint to Ayrshare events so you receive push notifications instead of polling:
mcp__ayrshare__register_webhook— subscribe an HTTPS URL to one event action.mcp__ayrshare__unregister_webhook— cancel a subscription by action.mcp__ayrshare__list_webhooks— list current subscriptions.
All three 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__register_webhook | Subscribe an HTTPS endpoint to a webhook action | POST /hook | url (must be https://), action (one webhook action) | source (string), secret (string — for signature verification) |
mcp__ayrshare__unregister_webhook | Cancel a webhook subscription | DELETE /hook | action (one webhook action) | source |
mcp__ayrshare__list_webhooks | List current webhook subscriptions | GET /hook | — | allWebhooks (bool), source |
Webhook actions (the action enum): feed, social, scheduled, batch, messages, mentions, comments, automations, accountActivity.
Auth
All three 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 manage one client profile's webhooks, or set the Profile-Key header (.mcp.json headers) to default the whole connection to it; with neither, calls manage the account's primary/Business profile. Beyond profileKey, these webhook tools take no passthrough object; their inputs are exactly the fields in the table above. Full model: ../getting-started/SKILL.md.
Usage guidance
urlmust be HTTPS.register_webhookrejects non-https://URLs. The endpoint must be reachable so Ayrshare can deliver events to it.- Pick the right
action. One subscription = one action. The actions arefeed,social,scheduled,batch,messages,mentions,comments,automations,accountActivity. - Confirming a queued post published — use
scheduled, don't poll.scheduledis the platform-agnostic post-completion webhook: it fires when a queued/scheduled post finishes processing. Register ascheduledwebhook to be told when the post goes out, instead of repeatedly calling history. Once notified (or if you can't run an endpoint), you can confirm details withmcp__ayrshare__get_post(Ayrshare Post ID) ormcp__ayrshare__get_post_history— but the webhook is the push-based, no-polling path. See../history/SKILL.md. - Use
secretto verify deliveries. Pass asecretat registration so your endpoint can verify the signature on incoming payloads and reject spoofed calls. sourceis a free-form tag you can attach at register time and then filter on withunregister_webhook/list_webhooks. Use it to distinguish multiple subscriptions for the same action or different downstream consumers.- Unregister by
action. To stop notifications, callunregister_webhookwith the sameaction(andsourceif you registered with one). To audit what's active, calllist_webhooks(allWebhooks: trueto widen the listing).
Gotchas
- Non-HTTPS URLs are rejected.
register_webhookrequireshttps://. A plainhttp://or hostless URL fails. - One action per call.
actionis a single value, not an array. To subscribe to multiple event types, register each separately. scheduledis the post-completion signal, notsocial. For "tell me when my queued post published," usescheduled(platform-agnostic, fires on post completion). Don't reach for polling loops when ascheduledwebhook does it push-style.- Be deliberate about scope. Which profile a webhook is registered/listed under is set by the
profileKeyargument (per call; it wins) or the connection'sProfile-Keyheader; with neither it's the primary profile. Confirm you're targeting the intended profile before registering. - Unregister must match how you registered. Cancel with the same
action(andsourceif used). A mismatchedsourcemay leave a subscription active — verify withlist_webhooks. - On failure, call
mcp__ayrshare__explain_error, then surface it — don't loop.register_webhook/unregister_webhookare writes: never auto-retry on a 4xx (bad URL, unknown action, wrong scope). Translate the error viamcp__ayrshare__explain_errorand present it; 429 gets at most one retry. (Mirrors the global retry-safety rule.)