Social Media Manager by SocialBu

2. Call `get_post_options` for those accounts. Check the actual format and media requirements before scheduling each entry. Read `list_posts` for each destination, following pagination, to compare the relevant dates against existing posts. Keep existing posts unless the user authorizes a change.
3. Resolve the final copy, account, actual media, dates/times, and requested state. Do not turn a planning request into a scheduling operation. If these choices are already clear and authorized, proceed without asking for repeated confirmation.
4. Convert each local time to UTC `Y-m-d H:i:s` using the offset on that date. Call `create_post` once per destination with an explicit `post_type: scheduled` and future `scheduled_at`. For saved drafts use `post_type: draft`; for requested team review use `post_type: awaiting_approval`. An existing draft selected for scheduling should use `update_post` with its ID, `post_type: scheduled`, and `scheduled_at`.
5. Supply accessible HTTP(S) media URLs or co

- Use `get_post_options` before creating or materially changing a post when network-specific options may apply.
- Interpret every scheduling timestamp as UTC in `Y-m-d H:i:s` format. Convert from the user's timezone when needed.
- Do not publish, delete, disconnect an account, approve or reject a post, change an automation, or remove listening data unless the user's request authorizes that action.
- If the user already gave clear authorization and the target is unambiguous, proceed without asking them to repeat it.
- Verify the destination account, content, media, scheduled time, and requested post state before a consequential action.
- Return the actual SocialBu result. Never invent a post, account, metric, publish result, or successful mutation.
- Explain actionable API or permission errors without exposing tokens, signed upload URLs after use, or private account data unrelated to the request.

## Connect

Connect the hosted MCP server at `https://socialbu.com/mcp` using Streamable HTTP and OAuth. Complete authorization in the user's browser on SocialBu. Keep passwords and access tokens out of chat and configuration files.

In OpenClaw, open **Settings → MCP**, add `socialbu` with that URL and the Streamable HTTP transport, and set `auth` to `oauth` in the scoped configuration editor. Select **Sign in**, complete authorization, then check the connection. Follow the [OpenClaw MCP connection guide](https://docs.openclaw.ai/tools/mcp) if the installed version uses different controls.