Blog post drafts Write SEO blog post drafts with Gemini CLI
Writing blog post drafts with Gemini CLI means asking Google's terminal agent for a post, confirming the cost, and having StoreSEO save the result as a draft article in your Shopify blog.
Last updated: October 2026
Set up Gemini CLI for StoreSEO
Skip this if Gemini CLI is already connected. The full guide, with the alternatives, is on the Gemini CLI page.
- 1
Add StoreSEO to Gemini CLI
Run this in any terminal. The user scope writes the server to ~/.gemini/settings.json so every project sees it. Without --scope user the command writes to the current project's .gemini/settings.json.
Terminalgemini mcp add --scope user --transport http storeseo https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Start gemini. The first time it calls StoreSEO it opens your browser: pick your Shopify store and approve access. If the window does not open, type /mcp auth storeseo inside Gemini CLI. Then gemini mcp list should show storeseo as connected.
Prompt/mcp auth storeseo
How does this work in Gemini CLI?
You run Gemini CLI in a terminal in the folder you work from and type the request: a 900 word post on caring for leather boots for the Journal blog, with a featured image. The model sees StoreSEO tools under names like mcp_storeseo_storeseo_list_blogs, and it calls storeseo_start first and then storeseo_list_blogs to find the numeric blog id. The CLI prints each tool call as it runs.
Gemini CLI asks you to confirm an MCP tool call before it runs unless the server has trust turned on. Leave trust off for StoreSEO. For storeseo_generate_blog_post, StoreSEO also tells the agent to state the AI credit cost, which grows with word count and the featured image, and to wait for your yes. You answer in the conversation and then at the CLI's confirmation prompt. The job then runs in the background for a few minutes while the agent polls storeseo_get_blog_post_job and reports progress.
When the job completes, the agent can read the draft's SEO record with storeseo_get_resource_seo, using the article id from the job result, and summarize what to fix. The article is a draft in Shopify. You review it, edit it and publish it from Shopify admin. If you want to limit what the model can reach, an includeTools list on the server can expose only the five tools this job needs.
-
You: Write a 900 word draft on caring for leather boots for the Journal blog, with a featured image.
- storeseo_start read-only
- storeseo_list_blogs read-only
-
Gemini CLI: Journal is synced. A 900 word post with a featured image will spend AI credit, more than text alone. Do you want me to go ahead?
-
You: Yes, go ahead.
- storeseo_generate_blog_post needs approval
- storeseo_get_blog_post_job read-only
-
Gemini CLI: Writing is under way, 2 of 5 steps done. I will check again and tell you once the draft is in Shopify.
What to ask Gemini CLI
Use StoreSEO to list my blogs and how many articles each one has.
Write a 900 word draft on caring for leather boots for the Journal blog with a featured image. Tell me the AI credit cost and wait for my yes.
Check the blog post job you started and report how many steps are done. When it finishes, read the draft's SEO record.
- List my blogs and write a 1,200 word draft on how to care for linen shirts in the News blog. Tell me the cost first.
- Write a draft post targeting best gifts for coffee lovers, with a featured image.
- How far along is the blog post you started?
- Check the SEO score of the draft you just wrote.
- Draft three post ideas for my store and write the strongest one.
What StoreSEO does: blog post drafts
StoreSEO writes a full blog post with AI and saves it as a draft article in the Shopify blog you choose, optionally with a featured image. Nothing is published: you review and publish from Shopify admin.
Requires: Spends AI Content Optimizer credit; the cost grows with word count and a featured image. Blogs must be synced in the StoreSEO app.
- 1
Pick the blog
The agent lists your synced blogs, the sections posts go into, with their ids. An empty list means the blogs need syncing in the StoreSEO app first.
- 2
Agree the brief and cost
Topic, keyword, length and whether to add a featured image. The cost grows with length and the image, so the agent tells you and waits for your yes.
- 3
Generate in the background
Writing takes a few minutes. The agent polls the job and reports progress, and does not present the post as finished while it runs.
- 4
Check the draft
When the job completes, the agent can read the draft article's SEO record. You review and publish the post from Shopify admin.
Blog post drafts reference
| Output | A draft article in the chosen Shopify blog, never published live |
|---|---|
| Featured image | Optional; uploaded with the draft and adds to the cost |
| Run time | A few minutes in the background |
| Insufficient credit | The call fails before anything is queued or spent |
| Blogs | Only blogs synced with StoreSEO are listed; syncing is done in the app |
| Failed runs | The job reports the error and credits are settled automatically |
Rules Gemini CLI follows
- The agent states the expected credit use and waits for your yes before it starts a post.
- Posts are saved as drafts only; publishing is done by you in Shopify admin.
- While the job runs, the agent reports progress and never presents the draft as finished.
In Gemini CLI
Do not set trust: true on the storeseo server. Trust skips every tool confirmation, so storeseo_generate_blog_post would run on the agent's say alone and the confirmation StoreSEO asks for in chat would be the only check. The browser sign-in also needs a browser on the same machine, so on a headless box or over SSH use the access token header, and then check that the token's connection still lists the blog tools. Google's site also says Gemini CLI was replaced by Antigravity CLI for unpaid tier and Google One users, so check which agent your account can use.
What runs without asking. Reads such as SEO scores, store listings, settings and Google reports run straight away. Generating a preview spends AI credit but writes nothing, and StoreSEO tells the agent to say what a generation will cost before it runs one. Applying content, optimizing images, changing settings, publishing llms.txt or agents.md, writing a product description and deleting anything wait for your yes in the conversation. That yes is an instruction the agent follows, not a lock on the server, so your client's own tool-approval setting is the hard stop.
Questions
Should I turn on trust for StoreSEO in Gemini CLI to speed up blog drafts?
No. Trust skips all tool confirmations, including the one for storeseo_generate_blog_post, which spends AI credit. Leave it off and approve the generate call when the CLI asks.
How do I limit Gemini CLI to just the blog tools?
Add an includeTools list to the storeseo server in settings.json naming storeseo_start, storeseo_list_blogs, storeseo_generate_blog_post, storeseo_get_blog_post_job and storeseo_get_resource_seo. The model then sees only those tools from StoreSEO.
Will the agent publish a blog post on my store?
No. StoreSEO saves generated posts as drafts in the Shopify blog you choose. You review and publish them from Shopify admin.
How long does a blog post take?
A few minutes. The writing runs in the background and the agent checks the job until it is completed, failed or cancelled.
What does a blog post cost?
It spends AI Content Optimizer credit, and the amount grows with the word count and with a featured image. If you do not have enough credit the call fails before anything is spent.
Why does the agent say I have no blogs?
Only blogs synced with StoreSEO are listed. Sync your blogs in the StoreSEO app, then ask again.
Keep going
Blog post drafts with other agents
More Gemini CLI guides