Use case · AI post drafter
Draft a WordPress post in one sentence.
The agent reads your existing posts to match your tone, drafts the new one, drops it as a draft. You preview, edit if needed, publish when ready. Never auto-publishes.
The problem you actually have
You have an idea. By the time you’ve opened the editor, fought the block editor for two minutes, and stared at the blank page, the idea has cooled. The post never gets written.
Generic AI writer tools (Jasper, Copy.ai) produce content that doesn’t match your tone — they have no read of your past posts. You end up rewriting most of the output and the time saved is marginal.
You want: type the angle in chat, the agent reads your last 5 posts on similar topics for tone, drafts the post, drops it as a draft. You preview, edit the parts that need editing (most agents nail 70-90% on first pass once they’ve read your style), publish when ready.
How the assistant solves it
You type the request in plain English inside wp-admin. The agent picks wp_create_post (plus wp_search_posts, wp_preview_post, wp_publish_post as needed) and walks the steps below.
- You ask: “draft a post about how our pricing changed last week, reference the announcement we shipped Tuesday.”
- The assistant calls
wp_search_postswith query “pricing announcement” to find the Tuesday post and read your existing tone. - It drafts the new post matching your style — same paragraph length, same level of formality, same conventions.
- It calls
wp_create_postwith title + content. Returns the draft ID and edit URL. - It calls
wp_preview_postto show you the draft inline in chat. - You ask for any edits in chat (“shorten the intro”, “add a callout for the Builder plan”) — each edit goes through
wp_update_post. - When ready: “publish it Friday at 10am.” — assistant calls
wp_schedule_post.
Before vs after
| Without the assistant | With the assistant | |
|---|---|---|
| Time from idea to draft | 20-40 minutes (open editor, fight Gutenberg, structure, write) | ~3 minutes (chat prompt, review, light edits) |
| Tone matching | Manual — you reread your last posts to recalibrate | Auto — the agent reads your last 5 similar posts before drafting |
| Risk of accidental publish | You hit “Publish” instead of “Save Draft” by mistake | Tool flow requires explicit wp_publish_post call after a preview confirmation in chat |
| Cited sources from your own site | You forget to link to your previous post on the topic | Agent automatically references prior posts via wp_search_posts and inserts internal links |
Where it stops
- For deeply technical or domain-specific posts (a niche legal post, an engineering deep-dive), the LLM may produce confident-but-wrong claims. Read every draft. The “preview first” rule is non-negotiable for a reason.
- The agent never auto-publishes. The flow is:
wp_create_post(draft) →wp_preview_post(preview in chat) → explicit “publish” / “schedule” →wp_publish_postorwp_schedule_post. - Tone matching is decent but not perfect. It picks up rhythm and word choice; brand voice nuance is harder. Plan to edit 10-20% of phrasing on first runs.
FAQ
Will it auto-publish if I tell it to?
Only after an explicit confirmation: you must ask for a preview, see the preview, then say “publish” / “go” / “schedule for X.” There’s no single-step “draft and immediately publish” path. By design.
Does it match my tone?
It reads your most recent posts on similar topics before drafting (via wp_search_posts). Tone matching is materially better than a generic AI writer that doesn’t see your past content.
Can it do scheduled posts?
Yes — wp_schedule_post. You say “publish Friday at 10am” and it sets the post status to “future” with the right datetime. Confirmation required.
Plan?
Admin or Bundle.
Stop writing the first draft yourself.
Free plan, no card. Or read the full admin assistant page.