Forem: Luca Restagno

Run a Weekly Threads Analytics Review From Claude (With a Custom Dashboard and Content Pillars)

Luca Restagno — Sat, 18 Apr 2026 07:08:54 +0000

Every Sunday I do a Threads review. I look at what performed, what flopped, and what I'll double down on next week. For a long time this meant opening five different tabs, copying numbers into a spreadsheet, and trying to spot patterns myself. Tedious work that I skipped more weeks than I'd like to admit.

Now I run the whole review from a single Claude conversation. Claude pulls the data, builds me a custom HTML dashboard, and proposes three content pillars for the week ahead. Takes about 5 minutes.

This is Post 4, the final post in the BlackTwist MCP Server series. Post 1 covered setup. Post 2 covered weekly content planning. Post 3 covered automated follow up replies. Today we close the loop with a data driven review.

Why Weekly Reviews Matter

Consistency beats complexity. You've heard that. But consistency without feedback is just stubbornness. You need to know if what you're doing is working so you can adjust.

A weekly review answers four questions.

What performed best and why.

What performed worst and why.

Is my audience growing.

What should I do more of next week.

If you can answer those four questions every week, your growth compounds. If you can't, you're running on hope. Hope is not a strategy.

The problem is that most creators don't run weekly reviews because the data is scattered. Per post analytics in one place. Follower growth in another. Engagement rates somewhere else. Building a clean picture takes time most people don't have on a Sunday.

The BlackTwist MCP Server fixes this. Claude pulls all the data in one conversation and presents it as a single dashboard. You read the dashboard, you understand the week, you plan the next one.

The Analytics Tools Claude Has Access To

Before the prompt, here are the tools Claude uses in this workflow.

get_live_metrics returns your current aggregate metrics. Views, likes, replies, reposts, quotes, engagement rate for a configurable time period. Claude uses this for headline numbers.

get_metric_timeseries returns a specific metric broken down by day. Useful for spotting trends. Did engagement climb through the week or did it spike on one day?

get_post_analytics returns engagement data for individual posts. This is how Claude identifies your top performers and your flops.

get_follower_growth returns your follower count over time. Did you grow last week? Lose followers? Break your personal record?

get_consistency returns your posting consistency data. How many days did you post? Longest streak?

get_daily_recap returns yesterday's numbers in a condensed format. Useful for a morning check in that isn't a full weekly review.

get_recommendations returns BlackTwist's personalized recommendations based on your data. Best posting times. Content angles that worked. Patterns Claude can't spot on its own.

Claude uses all of these in the weekly review. You don't need to remember the tool names. Just know that the data exists and Claude can grab it.

The Prompt That Runs The Whole Review

Paste this into a new Claude conversation with BlackTwist connected.

Run my weekly Threads review. Pull the last 7 days from BlackTwist:

Live metrics for the week compared to the previous 7 days

My top 5 performing posts

My bottom 3 performing posts

Follower growth day by day

Daily engagement rate over the last 14 days

Personalized recommendations from BlackTwist

Then build a visual dashboard as an HTML artifact summarizing the week. Use a clean minimal design. Show the key numbers at the top, the top and bottom posts in a table, the follower growth as a line chart, and the engagement rate as a bar chart.

Finally, based on what performed best this week, propose 3 content pillars I should double down on next week. For each pillar, give me the pillar name, why it worked this week, and 3 specific post ideas I can write.

Claude will work through this step by step. Here's what happens.

Step 1: Claude Pulls the Data

Claude calls the BlackTwist tools one after another. You'll see each tool call in the conversation as it happens.

Live metrics first. Then the top posts, bottom posts, follower growth, engagement rate timeseries, and recommendations. Each tool returns structured data that Claude reads and summarizes inline.

This step alone saves 15 minutes. Opening the dashboard, copying numbers, comparing tabs. Done in 30 seconds.

Step 2: Claude Builds the Dashboard

Here's where it gets fun. Claude takes all the data and builds an HTML artifact. In Claude on the web, artifacts render in a side panel next to the conversation. You see the dashboard in real time as Claude builds it.

The dashboard has four sections.

Headline metrics at the top. Total views this week, total engagement, follower change, engagement rate. Each one shows the week over week change as a percentage.

Top and bottom posts. Two tables side by side. Top 5 shows what worked. Bottom 3 shows what didn't. Each post has its text, views, likes, and replies.

Follower growth chart. Day by day line chart for the week. You see the shape of your growth.

Engagement rate chart. Bar chart showing engagement rate per day for the last 14 days. You see the rhythm and spot dips.

The dashboard is built on the fly for your specific data. No templates. No static reports. Just a visualization of your actual week.

You can export the dashboard as HTML or take a screenshot for your records. Some people save these week over week to build a visual history of their growth.

Step 3: Claude Proposes Content Pillars

The dashboard tells you what happened. Content pillars tell you what to do next.

After building the dashboard, Claude reads the data again and writes three pillar recommendations. Each pillar has a name, a reason it worked, and 3 specific post ideas.

Here's an example output from a real review I ran last week.

Pillar 1: The Consistency Floor Framework

Why it worked this week: Your top post was about how daily posting feels different when you treat it as a floor instead of a ceiling. It got 847 views and 62 replies, your highest reply count of the week. The phrase "consistency floor" resonated because it reframes a hard habit as something achievable.

Post ideas:

A before and after of what your calendar looked like before and after you adopted the consistency floor mindset

The exact minimum threshold you use (1 post per day? 3 posts per day?) and how you picked it

What happens on days when you can't even hit the floor (spoiler: you don't burn the streak)

Claude gives you three of these. Nine post ideas total. You take the best ones, feed them back into the weekly planning workflow from Post 2, and your content is set for the week.

This is the loop. Data in, pillars out, new content written, published, measured, back into the dashboard next week. Each cycle makes your content sharper because you're always writing toward what your audience actually responds to.

Workflow Variations

The full review prompt above is the deluxe version. Here are a few lighter variations you can run on different days.

Morning check in (2 minutes)

Give me yesterday's recap. New followers, posts published, best post of the day.

Claude calls get_daily_recap and summarizes in a few sentences. No dashboard. Just a pulse check.

Mid week temperature read (5 minutes)

Compare this week so far to last week at the same point. Am I on track to beat last week? If not, what do I need to change?

Claude pulls partial week data, compares against the same day last week, and gives you a focused answer.

Monthly deep dive (10 minutes)

Run my monthly review. Last 30 days vs the 30 days before. Top 10 posts. Follower growth trend. Best posting times. What should I change for next month?

Claude pulls a month of data, identifies bigger patterns, and recommends strategic changes instead of tactical ones.

Post specific postmortem (3 minutes)

My Tuesday morning post got 200 more views than my average. Pull the post, pull the data, and tell me what made it different from my usual content.

Claude finds the post, pulls its analytics, compares it to your baseline, and hypothesizes what made it work.

You can run these at different cadences. Morning check in daily. Temperature read mid week. Full review weekly. Deep dive monthly. Postmortem whenever something interesting happens.

The Part Where Claude Gets Smarter Than You

Here's a moment from last week's review that surprised me.

Claude pulled my data and noticed that my engagement rate was climbing Monday through Wednesday, then dropping sharply Thursday through Sunday. I hadn't spotted the pattern because I was looking at weekly aggregates. Claude saw it because get_metric_timeseries breaks the data down by day.

It asked: "Are you publishing different types of content early vs late in the week?"

I checked. Monday to Wednesday I was publishing personal stories. Thursday to Sunday I was publishing how to content. The personal stories were outperforming the how to content by 2x on engagement rate.

That's a finding I would have missed. I've been running this account for two years. Claude spotted it in a single conversation because it was reading the data fresh and pattern matching against the rest of the week.

The lesson: let Claude interrogate your data. Don't just ask for a summary. Ask why. "Why did Tuesday outperform Thursday?" "Why did this post get more replies than my usual?" "What do my top 10 posts have in common that my bottom 10 don't?"

Claude will give you answers based on your actual numbers, not generic creator advice from a podcast.

Common Questions

Does the dashboard update automatically? No. The dashboard is a snapshot of the data at the moment Claude built it. Run the review again next week to get a fresh dashboard.

Can I save the dashboard? Yes. Claude on the web lets you export the artifact as HTML. You can also screenshot it. Some people build a folder of week over week dashboards as a visual history.

Which plan do I need for the full analytics? Check your BlackTwist plan. Basic metrics (live_metrics, daily_recap) are on all plans. Advanced analytics (time series, post level analytics, recommendations) typically require a paid plan. If a tool fails, your plan is probably the reason.

Can Claude compare me to other creators? Not directly. BlackTwist doesn't expose other creators' data through the MCP Server. But Claude can use the BlackTwist monthly Threads report data (based on 20K+ posts from 255+ creators) as a reference if you ask it to. "Compare my engagement rate to the average in the Threads creator community."

What's the best day to run the weekly review? I do it Sunday evening. Gives me a clear plan for the week ahead. Some people do it Monday morning to start the week fresh. Pick whichever fits your workflow and stick with it.

Can I run this review on a schedule? Yes. Claude now supports scheduled tasks, so you can ask Claude to run this review automatically every Sunday and drop the dashboard into a new conversation each week. You can also connect Gmail, Slack, and other apps to Claude, which means the weekly report can land directly in your inbox or as a message in your Slack channel of choice.

Wrapping Up The Series

Four posts. One workflow.

Post 1: Connect Claude to BlackTwist and schedule a post through a conversation.

Post 2: Plan and schedule a full week in one sitting with your time slot format.

Post 3: Set up automated follow up replies so your best posts drive traffic while you sleep.

Post 4: Run a weekly review, build a custom dashboard, and let Claude propose pillars based on what actually worked.

Put them together and you have a complete Threads operating system. Planning, publishing, automating, measuring, iterating. All from Claude. All connected to your real data. All built on top of a content habit you already have.

The point isn't that automation replaces the work. The point is that automation removes the friction around the work so you can spend more time on the part that matters: writing things worth reading.

If you haven't connected the MCP Server yet, here's one more nudge. blacktwist.app/mcp/docs. Free on all plans. Setup takes 30 seconds. You can have your first automated Threads workflow running before the end of your coffee.

See you!

Set Up Automated Follow Up Replies on Your Best Threads Posts From Claude

Luca Restagno — Fri, 17 Apr 2026 18:15:27 +0000

Your best post this month probably deserved a follow-up and didn't get one. Mine did too. For months, I watched posts hit 200 likes and then just sit there. The attention came and went. I was busy with client work or asleep or eating dinner with my kid. By the time I saw the post blowing up, the moment was over.

The fix is automation. Set up a follow-up reply in advance. Define the trigger (say 100 likes or 30 replies). Write the reply. When the post hits the threshold, BlackTwist fires the reply automatically. Whether you're awake, online, or on a hike.

This is Post 3 in the BlackTwist MCP Server series. Post 1 covered setup. Post 2 covered weekly planning. Today we wired Claude to set up follow-ups for every post you schedule.

Why Follow-Ups Matter

A follow-up reply is a comment you post on your own post after it gets traction. Usually a link to something. Your newsletter. Your product. Your next post. A case study. An offer.

On Threads, the comment section is the second feed. When your post gets surfaced to new people, they don't just read the post. They scroll the replies. If your first reply is from you and it gives them somewhere to go, a real percentage will go.

The math is simple. If 10,000 people see your post and 5% read the comments, that's 500 people seeing your follow-up. If 10% of them click, that's 50 new clicks from a single post. Do that on 3 to 5 posts per week and your follow-up replies become a reliable traffic source.

The problem is timing. If you post the follow-up too early, the post doesn't have enough reach yet and the follow-up gets lost. If you post it too late, the moment is over and the scrollers have moved on. You want the follow-up to appear right as the post peaks.

Automated follow-ups solve this. BlackTwist watches the post. When it hits your trigger, BlackTwist posts the reply. You set it once and forget it.

The MCP Tools You Need

Claude uses a few specific tools to manage follow-ups.

get_follow_up_templates returns your saved follow-up templates. If you reuse the same "link to my newsletter" reply on every post, you save it as a template once and Claude applies it to new posts by reference.

get_thread_follow_up returns the follow-up configured on a specific post. Claude uses this to check if a post already has a follow-up or to read the current settings.

set_thread_follow_up creates or updates a follow-up on a post. This is the tool that does the work. You tell Claude the post, the trigger, the reply text, and the time delay.

You can do all of this from the BlackTwist dashboard. The point of using Claude is that you can handle it inline, in the same conversation where you draft the post, without switching tabs.

Workflow 1: Set a Follow-Up on Your Most Recent Post

Simplest case. You just scheduled a post and you want a follow-up on it.

Look at the last post I scheduled. Set up a follow-up reply that triggers when it gets 50 likes. The reply should say: If this was useful, I share one Threads growth idea per week in my newsletter. Link in bio. Use a 30 minute delay after the trigger.

Claude calls list_posts to find your most recent scheduled post, extracts the thread ID, then calls set_thread_follow_up with your parameters.

Three things to notice.

The trigger. You can set triggers based on likes, replies, reposts, quotes, or engagement rate. Pick whichever metric matters for the type of post. A question post? Replies trigger makes sense. An opinion post? Likes or quotes. A case study? Engagement rate captures the whole picture.

The delay. The delay is how long BlackTwist waits after publishing the original post before posting the follow-up reply. Set it to 30 minutes and the reply drops exactly 30 minutes after your post goes live. This gives the algorithm time to push the post before your follow-up appears. Replies from the post author can affect how the algorithm treats the post, so waiting lets the initial push complete.

The reply text. Keep it short. Keep it honest. The worst follow-ups are long marketing pitches. The best ones feel like a natural next thought from the author.

Workflow 2: Set Follow-Ups on an Entire Week

This is where it gets powerful. If you ran the weekly planning workflow from Post 2, you have 21 scheduled posts. Why set up follow-ups one by one? Let Claude do all 21.

For every post I have scheduled for next week, set up a follow-up reply. Use these rules:

Morning short posts = 50 likes trigger, 30-minute delay, reply promoting my newsletter.
Midday threads = 20 replies trigger, 45-minute delay, reply promoting my course.
Evening one liners = 30 quotes trigger, 60-minute delay, reply linking to the longer post on that topic if I have one.

First list all posts scheduled for next week. Then for each one, check if it already has a follow-up with get_thread_follow_up. If it does, skip it. If not, create one with set_thread_follow_up.

Claude walks through all 21 posts. For each, it checks if a follow-up exists, skips the ones that do, and creates the new ones.

This is a 5-minute workflow that would take an hour in the dashboard. And it's the kind of task you'd put off forever because it's tedious, which means your posts go out without follow-ups, which means you leave growth on the table.

Workflow 3: Smart Follow Ups Based on Post Type

You can get more clever. Ask Claude to pick the right follow-up based on the post's content.

For every post I have scheduled for next week, read the post text and decide what kind of follow-up makes sense.

If the post is about tools or software, the follow-up should link to my BlackTwist affiliate link.
If the post is about writing or content strategy, the follow-up should link to my writing course.
If the post is about personal stories or lessons learned, the follow-up should link to my newsletter.

Use 50 likes as the default trigger with a 30-minute delay. Tell me which posts you matched to which follow-up before creating anything.

Claude reads each post, classifies it, and creates a match map. You review the map, approve it, and Claude sets up all the follow-ups in one pass.

The power move here is catching mismatches. Sometimes Claude classifies a post wrong. You spot it, correct it, and Claude updates just that one. You never touch the dashboard.

Workflow 4: Review and Adjust Existing Follow Ups

Follow-ups aren't fire and forget. You should review them weekly to see what's working. Claude can help with this too.

Show me all my posts from the last 30 days that had follow-ups. For each, tell me: did the follow-up trigger? How much engagement did the follow-up itself get? And which follow-up text converted best?

This is where BlackTwist's analytics come in. Claude combines get_thread_follow_up with get_post_analytics to pull both the follow-up configuration and the post performance. You get a single report showing which follow-ups fired, which weren't, and which ones got replies.

From there you can tell Claude to update the underperformers.

The follow-up on the Tuesday post never triggered because it only got 40 likes. Lower the trigger to 25 likes for all future Tuesday posts.

Claude updates your templates or applies the new trigger to upcoming posts.

What Makes a Good Follow-Up

A few things I've learned from running hundreds of follow-ups.

Short is better than long. Two sentences max. The follow-up is a bridge, not a destination. Get people curious enough to click.

Specific links beat generic ones. "Link in bio" converts worse than a direct URL. If your platform allows it, use the direct link. Threads does allow links in replies (though not in the main post), so take advantage.

Credit the post. Something like "the idea in this post is from my newsletter, I write about this weekly" feels natural. Readers like knowing there's more where this came from.

Don't shill. "BUY MY COURSE NOW FOR 50% OFF" doesn't work. "I wrote a longer piece about this in my course if you want the full framework" does.

Match energy. If the post is personal and vulnerable, the follow-up should be warm. If the post is punchy and contrarian, the follow-up can be direct. Don't break the tone.

Common Questions

Does BlackTwist check the post every second? No. BlackTwist checks on a regular interval. If your post hits the trigger between checks, the follow-up fires on the next check. The delay you configure starts from when the trigger is detected, not from when it was actually hit.

Can I cancel a follow-up after I set it? Yes. Ask Claude. "Cancel the follow-up on my Tuesday morning post." Claude will call set_thread_follow_up with a delete flag.

What if my post doesn't hit the trigger? Nothing happens. The follow-up just doesn't fire. You don't pay a penalty. You can manually post a comment later if you want to.

Can I have multiple follow-ups on the same post? Not currently. BlackTwist supports one follow-up per post. If you want multi step follow-ups, schedule the second one manually once the first fires.

Does this work for Bluesky? Yes. Same tools. The trigger metrics are slightly different (Bluesky doesn't have quotes the same way Threads does), but the concept and the tools are identical.

Is follow up automation on the free plan? Check your plan. Some follow up features require a paid plan. If you're on the free plan and the set_thread_follow_up call fails, upgrade to Creator and try again.

What's Next

You now have a system for creating, scheduling, and maintaining follow ups across your whole content calendar. That's the growth engine running. But growth without measurement is just vibes. You need to know what's working so you can do more of it.

In Post 4 (the final post in this series), I'll show you how to run a full weekly analytics review from Claude. Pull the numbers, build a custom dashboard as an HTML artifact, and let Claude propose content pillars for the week ahead based on what actually performed. The last step closes the loop: good data in, good content out, better growth.

If you haven't connected the MCP Server yet, blacktwist.app/mcp/docs. You know the drill.

Plan and Schedule a Full Week of Threads Content From One Claude Conversation

Luca Restagno — Thu, 16 Apr 2026 06:17:35 +0000

Last week I scheduled seven days of Threads content in about 12 minutes. Three posts per day, 21 posts total, each one in a specific format, each one scheduled at the right time. All from a single Claude conversation.

This is Post 2 in the BlackTwist MCP Server series. Post 1 covered the setup and how to schedule a single post. Today we go wider. Full week planning, batched in one sitting.

If batching content has felt impossible because you can't hold the whole week in your head, this workflow is for you. Claude holds the plan. You steer.

The Format I Use

I post three times a day on Threads. Morning, midday, evening. Each slot has a specific format.

Morning is a short post. One idea, under 300 characters, easy to read while someone scrolls with their coffee. The goal is to get on people's radar early.

Midday is a thread. Three to six posts tied together, deeper angle, something worth stopping for. The goal is to give people who already follow me something to share.

Evening is a one liner. A single sentence, under 100 characters, sharp and memorable. The goal is to be the last thing they see before bed.

This format isn't the only way to run a Threads account, but it works for me. Consistency beats experimentation. If you have your own format, plug it into this workflow.

The Prompt That Does the Whole Week

Open Claude, make sure BlackTwist is connected (see Post 1 if you haven't done this yet), and paste this prompt. Swap in your own topics.

I want to plan and schedule a week of Threads content. My format is:

Morning (9am) = short post, under 300 chars, one clear idea
Midday (1pm) = thread of 3 to 5 posts, deeper angle on a topic
Evening (6pm) = one liner, under 100 chars, memorable

This week's themes: Monday = consistency, Tuesday = tools, Wednesday = analytics, Thursday = writing, Friday = community, Saturday = reflection, Sunday = preview next week.

First, check my time slots with list_time_slots. Then pull my top 5 posts from the last 30 days with list_posts so you can match my voice. Then draft all 21 posts in one document for me to review. After I approve, schedule everything. Don't post immediately, always use scheduled times.

Claude will work through this step by step. Here's what happens.

Step 1: Claude Loads Your Context

Before writing anything, Claude calls three MCP tools in a row.

list_providers to find your Threads account. This returns the provider ID Claude will use for all the posts.

list_time_slots to see your configured posting slots. If you already have 9am, 1pm, and 6pm slots set up in BlackTwist, Claude will use them. If you don't, Claude will schedule at those exact times without snapping to a slot.

list_posts with a filter for the last 30 days. This pulls your recent posts so Claude can match your voice.

This is the part most people skip. They ask Claude to write posts without giving it any context. The result is generic posts that sound like every other AI generated tweet on the internet. Giving Claude your recent posts as voice reference fixes this.

Step 2: Claude Drafts Everything in One Document

Claude writes all 21 posts into a single document in the conversation. Monday morning first, then Monday midday thread, then Monday evening one liner, then Tuesday, and so on.

Why one document? Because you want to see the whole week at once. Is Monday too heavy? Does Thursday overlap with Friday? Is Saturday missing a hook? You can't spot these problems if you're reviewing one post at a time.

Read the document. Mark the posts you don't like. Tell Claude what to change.

Post 4 (Tuesday thread) feels like a tool roundup. Rewrite it as a personal story about the one tool I use every day. Post 12 (Friday morning) starts too soft, give it a stronger hook.

Claude rewrites. You review again. Three rounds of feedback is usually enough to get a week you're happy with.

Step 3: Approve and Schedule

Once the content is dialed in, tell Claude to schedule everything.

Looks good. Schedule all 21 posts according to the times I specified. Confirm each day before moving to the next.

Claude schedules day by day. For each day, it calls create_post three times: once for the morning short post, once for the thread (which creates the parent post plus any child posts), once for the evening one liner.

The thread is the interesting one. When you create a thread, Claude passes an array of posts to create_post. The first post is the parent. The rest are replies that BlackTwist will publish as a thread when the scheduled time hits. You don't need to manage the threading logic. BlackTwist does it.

Claude will pause after each day and ask if you want to continue. This is intentional. You can stop mid-week if you change your mind, or keep going if everything looks right.

Once you approve the last day, you have a full week scheduled. Open blacktwist.app/calendar in another tab to see everything laid out.

Why Time Slots Matter

Time slots are a BlackTwist feature that deserves more attention. You configure your preferred posting times once (say 9am, 1pm, 6pm on weekdays, plus 10am and 4pm on weekends) and every new post snaps to the next available slot.

When Claude calls list_time_slots, it gets back your exact configuration. It can then match each day's posts to the right slot automatically. If Monday at 9am is already taken, Claude will use the next open slot on Monday (your 1pm) or move to Tuesday 9am, depending on what you asked for.

This is the difference between scheduling at random times and scheduling on purpose. Your best posting times stay consistent. Your audience knows when to expect you. The algorithm rewards that consistency.

If you haven't configured your time slots yet, do it before running this workflow. Open the BlackTwist dashboard, go to Settings, Time Slots, and set your morning, midday, and evening slots for each day of the week. Takes about 2 minutes.

What to Do When Claude Writes Something Off

Claude isn't always right on the first try. Here's how to fix the most common problems.

The posts all sound the same. This usually means Claude didn't weight your voice samples enough. Tell it to look at specific posts. "Reread post 2 from last week. Match that tone exactly for the Monday midday thread."

The threads are too long. Threads under 4 posts usually outperform longer ones on Threads. Ask Claude to cut. "Every thread is too long. Maximum 3 posts per thread. Cut the fluff."

The one liners are generic. One liners need a specific point of view. Ask Claude to be more opinionated. "The evening one liners feel like fortune cookies. Make them take a clear position on something."

The topics don't connect. If your week doesn't flow, tell Claude to thread a narrative. "Connect the days so Thursday references Monday and Friday references Tuesday. Build a story across the week."

The goal is iteration. Don't accept the first draft. Push Claude like you'd push a junior writer.

The Time Math

Planning a week the old way looked like this for me.

Sunday evening. Open a Notion doc. Write 21 posts from scratch. Two hours, easy. Copy each post into BlackTwist. Set the time. Click save. Another 30 minutes. Check the calendar. Fix mistakes. Total: roughly 3 hours.

With Claude and the MCP Server, the same week takes 12 to 20 minutes. Most of that is review and iteration, not writing from scratch. The scheduling step is a few seconds per post because Claude handles it.

That's 2.5 hours back every week. 10 hours a month. 120 hours a year. Use that time to talk to customers instead of staring at a content calendar.

Common Questions

Can Claude reference posts from more than 30 days ago? Yes. Just ask. "Pull my top 10 posts from the last 90 days." The list_posts tool supports date ranges.

What if I want to skip a day? Tell Claude. "Skip Saturday this week, I'm taking a break." Claude will plan 18 posts instead of 21.

Can I save the week as drafts instead of scheduling? Yes. Ask Claude to save as drafts. "Save all 21 posts as drafts, I'll schedule them manually later." The create_post tool has a draft flag.

Can I use this for Bluesky too? Yes. Same workflow. Change the provider or schedule to both Threads and Bluesky in one pass. "Schedule each post to both my Threads and Bluesky accounts."

Does this work on the free plan? Yes. The MCP tools used here (list_providers, list_time_slots, list_posts, create_post) are available on all plans including free. The free plan has a monthly post limit so check your subscription if you're scheduling a lot.

What's Next

A week of scheduled content is the foundation. The real growth happens when your best posts take off and you have a system to capitalize on the attention.

In Post 3, I'll show you how to set up automated follow-up replies that trigger when a post hits certain engagement thresholds. You schedule the post and the follow-up together. When the post pops, the follow-up fires automatically. It's the closest thing to a growth loop I've found on Threads.

If you haven't connected the MCP Server yet, go do it now. blacktwist.app/mcp/docs.

See you next on Post 3!

Schedule Threads Posts From Claude

Luca Restagno — Wed, 15 Apr 2026 21:44:11 +0000

I run my Threads account from Claude. I don't open the BlackTwist dashboard for scheduling anymore. I write the post in the same conversation where I'm brainstorming, tell Claude when to publish it, and the post lands in my queue.
This is the first post in a four-part series on managing Threads with the BlackTwist MCP Server. Here's what you'll get across the series.

Post 1 (this one). Connect Claude to BlackTwist in 30 seconds and schedule your first post through a conversation.
Post 2. Plan and schedule a full week of content with a morning short post, midday thread, and evening one-liner per day.
Post 3. Set up automated follow-up replies that trigger when your best posts take off.
Post 4. Run a weekly analytics review, build a custom dashboard, and let Claude propose content pillars for the week ahead.

If Threads is where you build your audience and Claude is where you already think, this series will save you hours every week.

Why Manage Threads From Claude

You already use Claude to draft posts. You brainstorm hooks, rewrite openers, and sanity check angles. But when it's time to actually publish or schedule, you switch tabs. Open BlackTwist. Paste the text. Pick a time. Click save. Switch back.

That tab switch is where your momentum dies.

The BlackTwist MCP Server removes the tab switch. Claude talks directly to your BlackTwist account and does the work for you. You describe what you want in plain English and the post lands in your queue.

There's another benefit most people miss. Claude already knows the context of your current conversation. The angle you're exploring. The audience you're writing for. The previous draft you rejected. When Claude schedules the post, it has all of that context loaded. You get a better post AND a faster workflow.

What You Need

A BlackTwist account with your Threads or Bluesky account connected. The free plan works for this tutorial. If you don't have one, sign up at blacktwist.app and connect your Threads account from the dashboard.

A Claude account. This tutorial uses Claude Desktop, but the same setup works for Claude Web, Claude Mobile, and Claude Code.

That's it. Two accounts. No coding required.

Connect Claude to BlackTwist

Claude on the web uses OAuth to connect custom MCP servers. You sign in once and Claude gets access to the BlackTwist tools.

Open claude.ai and start a new conversation. Click the tools menu (the plus button in the composer), scroll down, and click "Add connectors".

Claude will open the connector setup panel. Click "Add custom connector" and paste this URL:

https://blacktwist.app/api/mcp

Give it a name like "BlackTwist" and click Add. Claude will open a popup asking you to sign in with your BlackTwist credentials. Sign in, authorize the connection, and you're done.

Back in the conversation, click the tools menu again. You'll see BlackTwist listed with all the available tools: create_post, list_posts, get_live_metrics, get_recommendations, and more. About 22 tools in total.

Your First Scheduled Post

Now for the fun part. Start a new message and type something like this.

Schedule a post on Threads for tomorrow in one of the available time slots. The post is about how I use Claude to manage my Threads content. Keep it under 500 characters and make it feel personal.

Claude will draft the post, then call the BlackTwist MCP Server to schedule it. Watch what happens next.

First, Claude checks your connected accounts with list_providers to find your Threads account. Then it calls list_time_slots to see your configured posting times. This matters because Claude respects your existing schedule instead of picking random times.

If you haven't set time slots yet, Claude will schedule at the exact time you asked for. If you have time slots, Claude will snap to the closest one or ask you to pick.

Then Claude checks list_posts to make sure you don't already have something scheduled at that time. If there's a conflict, it tells you and offers to pick the next available slot.

Finally, Claude asks for confirmation before creating the post. This is important. You see exactly what will be published and when, before anything happens.

Approve the post and Claude calls create_post. A few seconds later, your post is in the BlackTwist queue, scheduled for 9am tomorrow.

Open blacktwist.app in another tab and you'll see the post in your calendar. It came from Claude, not from clicking around a dashboard.

What Just Happened Under the Hood

Claude used four MCP tools to do this. Worth understanding because you'll see them again in every workflow.

list_providers returns your connected social accounts. Claude needs this to know which account to post to when you have Threads, Bluesky, or multiple Threads accounts connected.

list_time_slots returns your configured posting times. This is how Claude respects your schedule instead of imposing its own.

list_posts returns your scheduled and published posts. Claude checks this to avoid conflicts and to reference past content.

create_post actually schedules the post. It takes the text, the provider ID, the scheduled time, and a few optional parameters like topic tags.

You don't need to memorize any of this. Claude handles it. But when you're debugging or trying a new prompt, knowing the names of the tools helps.

A Few Prompts That Work Well

Here are prompts I use regularly. Copy them and adapt to your voice.

Write a short Threads post about [topic] and schedule it for my next available morning slot.

I just finished a call with a client about [topic]. Draft a post sharing one insight from that call and schedule it for today at 1pm.

Schedule this draft for tomorrow at 9am: [paste text]. Keep the text exactly as is, don't edit it.

Take my last 3 top performing posts, find the common theme, and schedule a new post about that theme for tomorrow morning.

The last one is my favorite. Claude pulls your analytics, spots the pattern, writes a post in your voice, and schedules it. That's a five minute workflow that used to take 30.

Common Questions

Will Claude post without asking me? No. Claude always shows you the draft and asks for confirmation before calling create_post. You can also schedule as a draft instead of a scheduled post if you want to review later in the BlackTwist dashboard.

What if I don't like the post Claude drafts? Tell Claude to rewrite it. "Make it shorter." "Less formal." "Start with a question." You iterate in the same conversation until you're happy, then schedule.

Can I schedule to multiple accounts at once? Yes. If you have multiple Threads or Bluesky accounts connected, tell Claude which one to use. "Schedule this to my business account" or "Post this to both my Threads and Bluesky."

Does this work on Claude Mobile? Yes. The OAuth setup works the same way in the Claude mobile app. You get the same tools and can schedule posts from your phone without opening any other app.

Is the MCP Server free? Yes. The MCP Server is included on all BlackTwist plans, including the free tier. Post creation, draft management, and basic scheduling work at no cost. Advanced analytics features need a paid plan.

What's Next

You now have Claude wired up to your BlackTwist account, and you've scheduled your first post through a conversation. That alone saves a few minutes every day. The real payoff comes when you start planning in batches.

In Post 2 of this series, I'll show you how to plan and schedule a full week of content in one sitting. Morning short post, midday thread, evening one liner, seven days straight. All from a single Claude conversation.

If you want to try the MCP Server right now, head to blacktwist.app/mcp/docs. Setup takes about 30 seconds. No credit card required.

I Analyzed 21,864 Threads Posts in March 2026. Here's What I Found.

Luca Restagno — Wed, 01 Apr 2026 22:06:11 +0000

I'm Luca, co-founder of BlackTwist. We build scheduling and analytics tools for Threads.

We started BlackTwist because when we tried growing on Threads ourselves, we couldn't find real data about what actually works on the platform. Plenty of opinions. Plenty of "5 tips to grow" posts. Almost zero data.

So we started collecting it. We track about 2,000 Threads creators through our platform, and every month we publish what we see. No paywalls, no email gates. Just the numbers.

We do this because we think creators and marketers deserve to make decisions based on evidence, not guesswork. Threads is still a young platform. The playbook is being written right now, and we want the data to be part of that conversation.

This is the March 2026 report. Third month in a row.

The dataset

21,864 posts from 283 creators who had at least 100 followers and 1,000 views. Together those posts generated 26.5 million views at a 5.3% average engagement rate.

Long form threads get reach. Short posts get engagement.

This is a new finding. In our previous reports, long form threads won on every metric. This month, the picture is more nuanced.

Long form threads still averaged the most views per post at 4,416. That hasn't changed. If you want reach, write threads.

But short posts pulled a 6.09% engagement rate, the highest of any format. People are more likely to interact with a quick, punchy post than scroll through a multi part thread.

The takeaway for creators: use both. Long threads to grow your reach. Short posts to build relationships with the people already following you.

Saturday for views. Friday for engagement.

Saturday posts averaged 1,853 views per post, the highest of any day. We've seen this in every report now. Most people take weekends off. The creators who don't get rewarded with less competition and more visibility.

Friday had the highest engagement rate at 6.29%. If you want replies and likes, that's your day.

For marketers managing brand accounts, this means your Monday through Friday content calendar is leaving your best days uncovered.

5 to 6 posts per week is the sweet spot

One of the most common questions we get from creators is "how often should I post?"

The data keeps answering the same way. Creators who posted 5 to 6 times per week saw 8.87% median follower growth. That's roughly once a day with a day off. Sustainable, but consistent.

And the single strongest growth signal we track is replies. Creators who received 500+ replies in a month hit a 10.09% median growth rate. The Threads algorithm treats replies as the clearest sign that content is worth distributing. Likes are nice. Replies move the needle.

One creator grew 1,134% in a single month

@melodijoelperez went from 2,370 followers to 29,264. That's 1,134.8% growth in 30 days.

This is what keeps me excited about Threads. The platform is still actively surfacing new voices. 8 of the top 10 fastest growers started with fewer than 10,000 followers. Three started with fewer than 1,500. You don't need an existing audience to break through right now.

Here's the full top 10 by growth percentage:

@melodijoelperez: 1,134.8% (2,370 to 29,264)
@daltonspeers: 355.9% (306 to 1,395)
@realcodytye: 248.4% (1,339 to 4,665)
@jeremiah.2.0: 242.3% (142 to 486)
@zachmovesabroad: 175.4% (23,565 to 64,894)
@ummi.andrea: 160.6% (3,268 to 8,517)
@pak.thor: 139.7% (9,194 to 22,037)
@melusi_k: 125.8% (952 to 2,150)
@theladymystic: 119.0% (1,097 to 2,403)
@mitchelljasper.co: 116.4% (1,620 to 3,505)

And the top 10 by total followers gained:

@zachmovesabroad: +41,329 (23,565 to 64,894)
@melodijoelperez: +26,894 (2,370 to 29,264)
@justindavidcarl: +22,282 (78,935 to 101,217)
@heydearwomen: +14,325 (115,222 to 129,547)
@pak.thor: +12,843 (9,194 to 22,037)
@yestomomlife: +10,688 (27,486 to 38,174)
@lintropreneur: +10,271 (14,801 to 25,072)
@louisetilbrookdesigns: +10,087 (14,872 to 24,959)
@husseinnaji_: +9,603 (73,887 to 83,490)

The names that keep showing up

This is the part that fascinates me as a builder. Some creators appear on the leaderboard once and disappear. Others keep compounding.

@justindavidcarl gained 32,717 followers in January, 23,689 in February, and 22,282 in March. Three consecutive months on the leaderboard. That's nearly 80,000 followers in one quarter.

@lintropreneur went from 6,516 followers in January to 25,072 by the end of March. Four months ago they were a small account. Now they're firmly in the mid tier and still accelerating.

@zachmovesabroad appeared in the February report with 9,050 new followers and then exploded in March with 41,329. Momentum is real on this platform.

The pattern is always the same. Post consistently. Write long form. Generate conversation. Do it again next month.

The most viewed post was a short post

This surprised me. @mattstratton published a short post that hit 763,300 views with 5,800 replies and 1,900 reposts. One post. No thread. Just something that sparked a massive conversation.

@husseinnaji_ had the most engaging post at 688,400 views with a 1.71% engagement rate and 10,600 replies. The topic was healthcare and nervous system content. They appeared in the top posts list three times this month, all long form threads about health.

What this means for you

If you're a creator or a marketer trying to figure out Threads, here's what three months of data (over 65,000 posts analyzed) tells us:

Post 5 to 6 times per week. Daily is great. Seven days a week is unnecessary.
Mix formats. Long threads for reach, short posts for engagement.
Post on Saturdays and Fridays. Most people don't. That's your advantage.
Optimize for replies. The algorithm cares about conversation more than anything else.
Start now. Small accounts are breaking through every single month. The window is still open.

Why we publish these reports

At BlackTwist we believe the best way to help creators grow is to show them what actually works. Not what we think works. Not what some guru says in a tweet. What the data says.

We'll keep publishing these every month for as long as we're building this company. If you want the full interactive report with all the data tables, top posts, and creator leaderboards, it's free at blacktwist.app/report/march-2026.

I'm @luca.restagno.dev on Threads if you want to talk about any of this. And if you're a creator who wants to track your own analytics and schedule your posts, that's what we built BlackTwist for.