regenerate_blog_post
Re-run text generation for an existing post.
Re-run text generation for one existing post. Pulls from the post's stored outline or source content and rewrites the body. Find the postId with list_blog_posts.
Deprecated alias:
regenerate_postis still accepted butregenerate_blog_postis the canonical name.
Authentication: Required. Uses credits — available on any plan with credits remaining.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
syntheticId | number | Yes | The agent the post belongs to. |
postId | string | Yes | The post to regenerate. From list_blog_posts. |
Behavior
Returns immediately after enqueueing; generation is async. The post's status flips to generating and new text lands in roughly 30–90 seconds. Consumes credits — credit-gated, so it errors if you're out. The post must already have a stored outline or source content (posts created via workflows do). Poll list_blog_posts to see when it completes.
Published posts are rejected. Regeneration resets the post to a generating state and the worker returns it as a draft — so regenerating a live article would pull it off the public site. To edit a published post's body in place use update_blog_post_body (preserves published status); to rewrite from scratch, move_blog_post_to_draft → regenerate_blog_post → publish_blog_post.
Blog-only over MCP (MEE-1995): this tool operates on blog posts only. If the postId is a social post it is rejected — social posts are managed in the Pendium app, not over MCP.