Pipeline
- Fix the list, don't rotate it weekly
Competitor monitoring pays off through continuity. Pin 5–10 accounts first and write down in plain words who counts as a competitor. - Pull recent posts once a week
Take the last 10 posts with list_creator_posts and store only id, publish time, and likes/comments/shares. - Compute three numbers
① Median interaction of this week's new posts vs last week (week over week); ② post count (cadence shifts usually show up before the numbers do); ③ breakout rate = the share of posts whose interaction is more than 3x the account's own median. - Act only on anomalies
Interaction down more than 30% week over week, a sudden cadence shift, breakout rate at zero — only these three cases deserve reading post by post.
Real batch result
Example reading (one account, two weeks running)
Week 1: 5 posts, median interaction 12K, 1 breakout; week 2: 5 posts, median 8K, 0 breakouts → cadence is unchanged but efficiency dropped 33%, which means the direction is off. Look at topics, not frequency.
Week 1: 5 posts, median interaction 12K, 1 breakout; week 2: 5 posts, median 8K, 0 breakouts → cadence is unchanged but efficiency dropped 33%, which means the direction is off. Look at topics, not frequency.
Endpoints you need
What this article uses list_creator_posts, with the parameters below; use REST when writing code and MCP when wiring a client — both return the same data.
Copy and run
cURL
curl -s https://lucydomi.com/mcp/v1/list_creator_posts \
-H "Authorization: Bearer $BUSYBEE_API_KEY" \
-H "Content-Type: application/json" \
-X POST \
-d '{"platform": "tiktok", "creator": "yourcoffeedude", "limit": 10}'Python (standard library)
import os, json, urllib.request
KEY = os.environ["BUSYBEE_API_KEY"]
req = urllib.request.Request(
"https://lucydomi.com/mcp/v1/list_creator_posts",
data=json.dumps({"platform": "tiktok", "creator": "yourcoffeedude", "limit": 10}).encode(),
headers={"Authorization": f"Bearer {KEY}", "Content-Type": "application/json"},
method="POST",
)
data = json.load(urllib.request.urlopen(req, timeout=60))
for it in data["items"]:
print(it.get("url"), it.get("text", "")[:60])FAQ
Can the API return historical series directly?
No. Every call returns a snapshot of the present, so you have to land the history in your own store; that is also why the script should be idempotent (re-running it in the same week creates no duplicate rows).
How many accounts should I monitor?
5–10. One call per account per week keeps cost predictable; past 20 you end up with data nobody reads.
What if the numbers don't match the platform's own dashboard?
Public interaction counts refresh asynchronously, so the API returns the public value at that moment; when reconciling across sources, compare figures from the same point in time.
Related reading
One key, six platforms
Same fields, same MCP endpoint — switching platforms changes one parameter. Signing up credits you with $0.2 to try it.
View pricing Try one call