SMF·METRICOOL
Can a prompt replace Metricool?
Social media — social scheduling and content repurposing
Exhibit tracking slip
Verdict
Scheduling to one network through its official API is a weekend. What Metricool sells is the other side of the loop: the post you published on Tuesday comes back on Friday with its reach, saves and follows attached, across every network at once. Each of those metrics endpoints has its own permissions, its own rate limits and its own habit of changing, and keeping five of them working is the actual subscription.
Exhibit A — The prompt
Received on31.07.2026Build a personal social scheduler that closes the loop by pulling published-post metrics back in.
Pick exactly one network and implement it properly. Register a developer app, run the documented OAuth flow, store the access and refresh tokens encrypted, and handle expiry by prompting a reconnect rather than failing silently.
Publishing side: a composer with a live character count against that network's real limit, media upload with validation of file size, dimensions and aspect ratio before the post can be queued, and a week-view calendar to place posts. A background worker publishes at the scheduled time through the official API, with idempotency keys so a retry after a timeout cannot double-post, and stores the platform's returned post ID.
Metrics side, which is the point of this build: a second scheduled job re-reads each published post's insights at 24 hours, 7 days and 30 days after publication and appends a row to a metrics table. Store impressions, engagements, and whatever follower-attribution the network exposes. Never overwrite an earlier reading; the shape of the curve is the useful part.
Dashboard: posts sorted by 7-day engagement rate, best posting hour derived from your own history rather than a generic recommendation, and a per-post detail view with the metric curve plotted over time.
Out of scope, and say so in the README: connecting a second network, any form of scraping or unofficial API use, competitor tracking, ads data, and a link-in-bio page. Each additional network is a fresh app review, not a config change.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 every network beyond the one you got API access approved for
- B.2 the link-in-bio page and its click tracking
- B.3 competitor benchmarking against accounts you do not own
- B.4 the ads reporting pulled from Meta and Google
Prior art
Exhibit C — Why people still pay: API access, connector upkeep, and collaboration
Because platform API approval is a process, not a switch. Getting a personal app past review on each network, and keeping it there as terms change, is work that never ends and never ships a feature.
Questions
Can I import my scheduled queue from Metricool?
Partly. Metricool exports planned posts as CSV, so text and scheduled times come across. Media does not, and posts already published stay in Metricool's own analytics, so the metrics history starts empty here.
How hard is getting API access?
It varies enormously. Some networks approve a personal app in days with a written use-case description; others require a business verification and reject read-access requests for anything they consider analytics. Check the specific network's current policy before starting, because it decides whether the metrics half of this build is possible at all.
What does it cost to run?
A small VPS plus PostgreSQL, roughly five to ten dollars a month. The APIs themselves are free at personal posting volume; the cost is entirely the always-on machine that runs the scheduler and the metrics poller.
What is the one thing that does not survive the rebuild?
Seeing all your accounts in one place. This build connects one network, and the second one is not a setting — it is another developer account, another review, another set of rate limits, and another endpoint that will change shape without warning.
Related tools
Receipt