PostBazooka

PostBazooka MCP

PostBazooka stores your social ideas, posts, media, schedules, publishing results, insights, and human feedback. Agents manage their own research and work.

Connect at https://postbazooka.com/mcp. Call get_workflow first, read its instructions, and copy structuredContent.workflowVersion exactly into later calls. Refresh only after workflow_version_outdated; retry the unchanged intent with the same request ID.

Tools

Intent	Tool
Find or inspect content	get_posts_and_ideas
Create sourced ideas	create_ideas
Create posts with optional media	create_posts
Change text, media, channels or schedule together	edit_post
Change schedules for up to 100 posts	update_schedule
Change one image	update_post_image
Change shared or network-specific text	update_post_text
Find publishing results and performance	get_posts_insights
Find projects	get_projects
Find connected accounts	get_connections
Create a project	create_project
Move up to 100 posts to Recycle	delete_posts
Get website instructions for deleting a project	delete_project
Read human feedback	get_feedback

List tools support cursors and page sizes of 1–50, defaulting to 25. Content search defaults to active posts and ideas, newest first. Use IDs for existing content, or search/filter by project, network, connection, status, dates, and recycle state. Schedule ordering selects upcoming scheduled posts. Filters apply before pagination; keep the same filters when following a cursor.

For get_posts_and_ideas, get_posts_insights, get_projects, get_connections, and get_feedback, never request limit: 100. To retrieve 100 results, request limit: 50 and follow page.nextCursor with the same filters until enough results are returned or the cursor is absent. Read ID filters accept at most 50 IDs. Creation batches accept 1-10 posts or ideas; schedule and deletion batches accept 1-100 posts. These mutation batch limits do not increase read page sizes.

Editing and scheduling

Omitted edit fields remain unchanged. Content/media edits create a revision; schedule-only edits preserve the revision and reactions. Focused tools use the same editing implementation. Media can come from generated data/URLs, user-owned URLs, licensed URLs, or a media ID returned on existing content. A media replacement must include valid provenance and rights.

Both edit_post.schedule and each update_schedule.updates[].schedule accept:

• action: schedule, destination IDs, and an exact ISO scheduledFor more than 30 seconds ahead and within 30 days.
• action: unschedule and destination IDs; omit scheduledFor.
• action: publish_now and destination IDs; omit scheduledFor.

Combined edits validate and commit together. Immediate delivery starts after the durable commit. Report the actual delivery state: accepted or publishing is not Published. Batch requests return independent post outcomes.

Each write needs a unique requestId. Reuse it only for an exact retry. Single writes confirm operation.operationCommitted: true with the matching operation name and request ID. Batches return POSTBAZOOKA BATCH COMPLETED and an independent success and operationCommitted per post. A publishing deletion can succeed without changing state. Report each outcome; do not claim success from missing output or automatically perform a verification read.

Feedback

Before researching ideas or drafting posts, discover recent feedback with get_feedback using feedbackType: all and read: all. Apply relevant audience guidance and follow all relevant pages. For a gap longer than 24 hours, set from to your last review time. Filtering read: unread returns comments only and would miss likes, dislikes, and edits. Agents manage their own review process; read receipts are not completion tracking.

Likes are feedback, not automatic scheduling or publishing authorization. You or your agent choose explicit publishing times. A dislike on a post moves it to Recycle; interpret each reaction in context rather than treating one reaction as a broad audience preference.

get_feedback defaults to all human comments, reactions, and edits from the last 24 hours, including recycled content. Filter by dates, item, project, network/connection, feedback type, or comment read/unread state. Only comments returned on the current page are marked read. Read state is shared across agents and means retrieval, not understanding or action. Historical agent replies remain visible; there are no work leases, review states, or retries.

Recycle and website actions

Deleting posts moves them to Recycle without recording a dislike. An already-publishing post continues unchanged; the response reports success with its actual delivery state, and recycling follows a conclusive outcome. This never deletes content from a social network. Restore through edit_post with restore: true; deleted media must be replaced before scheduling.

The website is the visual feed. Scheduled filters the same feed. Project deletion and account connection management require the website; delete_project only returns instructions. Never request credentials in chat.