posterly

View saved version →

---
name: posterly
description: >-
  Use posterly to draft, validate, schedule, and manage social posts across
  18 platforms, inspect connected accounts and brands, prepare media,
  review analytics, or manage supported social inboxes and Google Business reviews.
---

# posterly

Use the connected posterly MCP server for social media work. It uses the user's
posterly OAuth connection. Do not ask for API keys, passwords, social credentials,
or payment details in chat. Call the actual tools exposed by the connected server;
its current schemas take precedence over examples in this skill.

Return only information needed to answer the user's request. Use internal account,
workspace and user IDs privately for tool calls. Do not print those IDs, trace
metadata or unrelated account details unless the user explicitly needs them.

## Discover

1. Call `whoami` to resolve the authenticated user, allowed workspaces, and scopes.
2. Call `list_accounts` to discover real account IDs and platforms. For a named
   client or brand, use `list_brands`, `list_brands_accounts`, and `list_brands_profile` for account
   membership and saved context. Never guess an account ID or cross workspace boundaries.
3. Use `list_platforms_schema` and the selected `account_id` before
   setting platform options. For general capability questions, use its default
   platform view. Planned platforms are not supported publishing destinations.
4. If authentication fails, direct the user to connect or reconnect posterly
   through the host's OAuth flow. For missing API entitlement, give the returned
   requirement neutrally. Link only to a verified informational entitlement
   page that does not initiate a purchase. Do not follow returned checkout or upgrade links. Never retry a denied call
   with different credentials or fabricate a successful result.

## Draft, validate, and schedule

Resolve the destination account, workspace, caption, media, settings, and timezone.
Use the user's timezone when provided; clarify ambiguous local times. Pass an
explicit IANA timezone to `find_available_slot`. Convert a chosen publish time to
an ISO 8601 timestamp with its UTC offset before creating the post.

Before validation or scheduling, check that the selected slot is still in the
future. posterly treats a timestamp within 60 seconds of now as immediate
publishing. If a next-free slot becomes stale or too close, request fresh slots
and use a returned future slot. Do not invent a timestamp or resume publishing
to work around an intentional publishing pause. A future preview can validate
while publishing remains paused; actual delivery remains held by that pause.

Draft in chat or use `generate_captions` when requested. It returns caption
options and uses Caption Assist quota; it does not save or schedule a post.
Then call `validate_post` and show a readable preview of the exact caption,
account, platform, media, workspace, and local scheduled time.

Call `create_post` with `confirm: true` only after the user approves those details.
For a batch, show every item and obtain approval for the whole batch before
calling `create_posts_batch`. Never omit `scheduled_at` unless immediate
publication is explicitly approved. Scheduling is a write that can later publish.
Changing approved content or destination requires renewed approval.

Report the returned post ID, status, and schedule. A scheduled or queued post is
not a published post. If a call times out or a batch partially succeeds, inspect
the saved posts before retrying to avoid duplicates.

## Media

Chat attachments are not automatically accessible to the hosted MCP server.
For a local file in ChatGPT, use `create_media_drop`, show the returned upload
link, then use `list_media` with the returned drop session ID. Use the stored
public URL in the post and validate it before requesting approval.

For a public HTTPS file, use `upload_media_url` with `url`. For a client that can
upload bytes directly, `create_signed_upload` returns a

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: setup
description: Connect posterly through OAuth, check accessible workspaces and social accounts, and guide the first validated social post.
---

# Set up posterly

1. Probe the existing connection once with `whoami`. If it works, reuse it.
2. If disconnected, use the ChatGPT or Codex plugin connection flow and sign in
   to posterly through OAuth. Passwords and OAuth consent stay in the browser.
   Never ask the user to paste an API key or password into chat.
3. Read the returned workspace permissions. If posterly
   reports missing subscription or API access, explain the returned requirement
   neutrally. Link only to a verified informational entitlement page that does
   not initiate a purchase. Never display subscription offers, initiate new subscriptions
   or upgrades, sell credit packs, or link to checkout, even if requested.
4. Call `list_accounts`. If no account is connected, use `list_platforms_connect_link` or `create_connect_session` for the user's chosen
   platform. Guide the browser handoff. Poll using `list_accounts_connect_session` and the returned session ID when applicable.
5. Resolve one account and the user's timezone. Draft a caption, find a suitable
   slot, and run `validate_post`. Show the exact destination, content, media,
   and scheduled time. Ask for approval before `create_post` with `confirm: true`.
6. Report the saved post ID and actual status. A scheduled post has not yet
   been published.

Use the main posterly skill for subsequent work. Help is available at
https://www.poster.ly/about and https://www.poster.ly/mcp.