Social workflows depend on the platforms, workspace and tool actions enabled during onboarding. A connected social account in a web application does not prove that every operation is available through MCP.
Prepare the brief#
Specify the brand, audience, channel, campaign goal, language and timezone. Include approved facts and asset requirements. Keep the scope small enough to review before scheduling or publishing.
Use only my enabled Social read tools to inspect the approved
test workspace. Summarise the content items returned for the
agreed date range. Do not create, schedule or publish anything.Draft and review#
If draft creation is enabled, prepare a single test item first. Verify the target workspace, channel, text, links and media. Check that any asset is approved for use and that the language matches the intended audience.
If the connection provides reads only, prepare the draft in conversation and complete publishing through your normal approved process. Do not treat a written caption as a scheduled post.
Schedule or publish#
An authorised scheduling task needs the exact destination, final content, date, time and timezone. Publishing may depend on the social platform's permissions and media requirements. A queued job does not prove that the post is live.
Verify the result#
Check the source record and final destination when the tools expose them. If an operation fails or times out, inspect its state before retrying to avoid duplicates. Report any unsupported media or platform restriction with the relevant error and without access tokens.
See drafts and write actions for the review workflow and usage and limits for retries and throttling.