How to run a weekly LinkedIn routine from your AI assistant
With MediaPilot connected to an AI assistant, a week of LinkedIn fits into one conversation. This guide gives the seven requests, in the order that works. Look at last week, clear the comments, check the queue, choose topics, draft, edit, schedule — with what the assistant does behind each, and where to slow down. It assumes the connection exists already — MCP is part of MediaPilot's Growth and Scale plans — and that you, not the assistant, decide what is published.
Open with last week's numbers
Ask: “How did my LinkedIn posts do over the last seven days, and over the last thirty?” The assistant reads your analytics for both periods — impressions, reactions, comments, shares, clicks and engagement rate — and names the posts with the most impressions. LinkedIn reports once a day, so this morning's post has no figures yet. Do not judge anything on one week; the reason to ask first is to have last week's strongest post in the conversation when you choose what to write next. Reading costs no credits.
Clear the comments before you write anything new
“Which comments on my posts have not been answered?” returns the open ones, newest first, each with the post it belongs to. Comments are synced every three hours, so the latest may not be there yet. For any that deserve more than a thank-you, ask for a suggested reply: it is written in your workspace's voice and within your comment rules, costs 1 credit, and is only a suggestion — you send it yourself from MediaPilot under Community. If your rules leave a comment to a person, the assistant says so instead, at no cost.
Look at the queue, then decide how many posts you need
“What is scheduled, and for when?” lists the posts already in the queue with their times. Now do the arithmetic yourself: if you post on Tuesday and Thursday and Thursday is covered, you need one post, not five. Batching is useful; drafting more than you will read carefully is how unread posts get published. Ask for the open drafts too, because the best next post is often one you started last week and left.
Choose topics from the pool, or bring your own
“What does MediaPilot suggest I write about?” reads your topic pool: subjects built from your profile, your links and your documents, each with who it is for, what it says and why it matters. Choose the one you can add something to this week — a call, a figure, a mistake — rather than the one that sounds best. If something happened that is not in the pool, describe the post yourself; a rough thought is enough. New topics are generated in MediaPilot itself, not from the chat.
Ask for the drafts one at a time
“Draft a post on the second topic, and work in what the client said on Monday: …” starts a draft in your workspace's voice. It takes about a minute, so the assistant receives a job reference and checks back. A draft costs 1 credit, or 4 with an image, and you can choose the kind of image: a scene, a quote card with one line from the post, or a card with the post's list or steps. Say “without an image” where you will add your own. Nothing is scheduled or published at this stage.
Read each draft in full and edit it in place
A list of drafts shows only the opening of each, so ask for the whole text. Read it for what an assistant will not catch on its own — a claim you cannot back, a sentence anyone could have written, an opening that warms up. Then say what to change. The assistant rewrites the draft in MediaPilot, and editing costs no credits. If you worked out better wording in the conversation, tell the assistant to use exactly that text.
Schedule with the account and the time zone spelled out
“Schedule the first for Tuesday at 08:30 Central European Time on my personal profile, and the second for Thursday at the same time on the company page.” The assistant looks up your connected accounts and puts each post in the queue; from then on MediaPilot publishes it on its own through LinkedIn's official API. Always name the time zone: a time without one is read as UTC, which in Zurich or Berlin is an hour or two out. Then ask for the queue once more and check both entries yourself.
Once it works, schedule the reading half
Checking numbers, comments, the queue and the topic pool is all reading, and reading costs no credits, so that half is safe to automate. On Claude's paid plans a scheduled task can use your connectors: “Every Monday at 08:00, report last week's numbers, the unanswered comments and what is in the queue, and suggest three topics from the pool.” The briefing is waiting when you sit down. Keep drafting, editing and scheduling for the sitting itself; those are the steps that need a reader.