OpenPostTasks and troubleshooting
Review schedules, create drafts, and diagnose connection or delivery failures.
Name the OpenPost workspace in every task after the first connection check. Tell the assistant whether it may change data and where it must stop for review.
Review a schedule
Use mcp:read:
Review next week's scheduled posts in the Personal workspace. Group them by destination, flag empty days and missing media, and do not change anything.The assistant can inspect posts, variants, connected accounts, media, and posting slots without gaining write access.
Check provider readiness
Use mcp:read before planning work for a new destination:
Check whether the Company workspace and its LinkedIn account are ready to publish an image post. Report each blocker without changing settings.This prevents the assistant from drafting against an unavailable provider, disconnected account, or unsupported format.
Prepare a draft
Use mcp:full, but stop before scheduling:
Create an unpublished launch draft for the Company workspace and its connected LinkedIn account. Reuse the newest matching image in the media library. Stop after creating the draft.Inspect the saved Post in OpenPost. Check each destination Variant before asking the assistant to schedule it. To adapt one message for several channels, use the adapt_post_variants prompt with the saved post_id and the variants[] arguments.
Select mentions
Use lookup_mentions with workspace_id, account_id and query before drafting a selected mention. It requires read access and searches through that account's grant. For LinkedIn, supply the exact company page vanity name.
Pass the returned target and label in publication segment settings.mentions, with version 1 and UTF-8 byte ranges. create_post and update_post accept ordered segments and structured rendition segments, including joined source overrides. Keep selected identities paired with their text when changing a thread. See the HTTP mention contract.
Choose identities separately for each network. Ask the user to choose when search returns several plausible accounts, and report provider permission or rate-limit errors. Do not substitute an account with a similar name.
Schedule approved work
Use mcp:full and provide an exact time or ask for an available posting slot:
Validate Post post_123. If it passes, schedule it in the next available Company workspace slot. Report the saved time and job state.Treat scheduled and queued as intermediate states. They do not prove that a provider published the content.
Investigate a failed destination
Use mcp:read first:
Inspect Post post_123, its variants, and lifecycle events. Explain which destinations succeeded or failed and quote the saved failure reason. Do not retry anything.list_posts already summarizes failures per Post as failed_variant_count with a curated error_kind, error_action, and error_message. Ask for get_post only when a failure needs full delivery detail.
Grant mcp:full only if you then want the assistant to make a correction or retry an authorized destination.
Fix a connection
| Problem | What to check |
|---|---|
| No OpenPost tools | Refresh the client's MCP metadata or start a new session. Enable the server's tools in the chat. |
| Login expired | Reconnect through OAuth or replace the expired developer token. |
| Wrong workspace | Check the signed-in account and token binding. A workspace-bound token cannot access another workspace. |
| Private server unreachable | Run the local bridge on a machine that can reach OpenPost, or provide a public HTTPS origin for cloud clients. |
| Bridge command missing | Configure the absolute path returned by command -v openpost-mcp. Run it as the user who saved the CLI profile. |
Inspect recent calls under Settings > Personal > Developer access for the client, tool, workspace, result, and failure reason.
Review Inbox mentions and business reviews
Use list_inbox with workspace_id and kind: "mention" or kind: "review". Follow its next_cursor, and use get_inbox_item for native context, moderation and operation receipts. These tools read stored state and work with mcp:read.
With mcp:full, refresh_inbox queues collection, set_inbox_state changes shared read/archive state, and mark_inbox_read marks all matching unread items across every page. act_on_inbox_item queues only supported actions. Supply a stable client_operation_id for that exact intent.
A Google review reply replaces the location owner's one reply. delete_reply removes only that reply. Never infer delivery from admission, or approval from delivery. Inspect the job and Google moderation state before another replacement. See the Inbox guide for account permissions and recovery.