Schedule social media posts from Gemini CLI

Why use a terminal agent for social media

Gemini CLI is handy when your content already lives in files: Markdown docs, release notes, a folder of blog drafts, a CSV exported from another tool. Instead of opening each file and copying text into a web form, you point Gemini at the folder and ask for posts. With Postika connected, the result is not a text file to paste later but real entries in your calendar.

Gemini calls list_channels to learn each network's limit and media rule, so it knows that X takes 280 characters and that a Pinterest pin needs an image. Then it calls create_post with a date in the project's own time zone. The protocol is explained in our MCP glossary entry.

A batch from a folder of drafts

Say you keep blog drafts in content/posts/. One prompt can do a week of promotion:

1. "For each post in content/posts published this month, write a LinkedIn post and a Threads post."
2. "Spread them over the next two weeks, one per weekday at 08:30, in approval mode."
3. Gemini reads the files, checks your calendar with list_posts to avoid doubles and creates the posts.
4. You open Postika, review the per-network previews and approve.

The same idea applied to a newsletter is what we call content repurposing. If you want this to run with no chat at all, an n8n workflow or a cron job calling the REST API is the better tool.

What stays in the app

Media cannot be passed through MCP. Instagram, TikTok and Pinterest posts need a photo or video and YouTube needs a video, so Gemini should leave those as draft or approval; you attach the file in Postika. Text-only networks (Facebook, X, LinkedIn, Threads) can be scheduled end to end.

Postika also does not do analytics or reply to comments; it is a calendar and a publisher. Plans are priced by connected channels, not by users or AI calls: Standard is €29/month for 5 channels, and every plan includes the MCP server (pricing). Other terminal agents work the same way, see Claude Code.

Running Gemini CLI non-interactively

Gemini CLI can also take a prompt as an argument, which makes it usable from a shell script or a scheduled job on your machine. A weekly script that asks "read this week's notes in notes/weekly.md and create a LinkedIn post pending approval for Monday at 09:00" gives you a recurring post without building a full automation. Keep the mode on approval for anything that runs unattended: the post appears in your calendar as pending, and you decide on Monday morning whether it goes out. If you manage several brands, name the Postika project in the prompt so Gemini does not have to guess.