Catch 'I'm cancelling / switching' posts across X, Reddit and forums and prioritize the loudest accounts for a save.
https://apidirect.io/mcp?token=YOUR_API_KEY
Use the churn-intent-saver skill: Who's threatening to cancel or switch away from {brand} right now, and which ones have the biggest audiences?
churn-intent-saver) makes your agent run this exact playbook instead of improvising its own searches.
In clients that support MCP prompts (Claude Desktop, Claude Code, Cursor) it also appears as a prompt named
churn-intent-saver, and any agent can call
get_skill(skill_id="churn-intent-saver") directly.
Monitors X — and optionally Reddit and product forums — for explicit churn intent about your brand, sizes each X author's reach, and pulls context so you can intervene before they're gone — biggest megaphones first.
Who it's for: Support, success and social teams doing proactive saves.
| Input | Required | Description | Example |
|---|---|---|---|
brand |
Yes | Your brand/product to monitor for churn and switching intent. | API Direct |
platforms |
No | Comma-separated list of platforms to run — options: twitter, reddit, forums. Omit to run all of them; name specific platforms to limit the run. | twitter, reddit, forums |
depth |
No | How many result pages to pull per platform (maps to each tool's pages/page param). Higher = more candidates, more cost. | 2 |
time_window |
No | Freshness filter for the forums sweep (maps to the forums time param). Keep recent so saves are still actionable. | week |
search_twitter(query="(cancelling OR \"switching from\" OR \"done with\") {brand}", get_sentiment=true, sort_by=most_recent, pages=2)
Core (always runs): surface explicit churn-intent posts about {brand}; keep negative-polarity ones. Use {depth} to control how many pages to pull.
twitter_user_profile(username=<author>)
For each churning X author from step 1, pull followers_count and verification to size each account's blast radius.
twitter_user_tweets(username=<author>, get_sentiment=true)
Read <author>'s recent tweets for context on why they're leaving so you can draft a tailored save.
search_reddit(query="{brand} (cancelling OR \"switching from\" OR \"done with\")", get_sentiment=true, sort_by=most_recent, page=2)
Only run if {platforms} includes reddit: catch the same cancellation/switching intent in subreddit threads; keep negative-polarity posts and note the subreddit as added context for the save.
search_forums(query="{brand} cancel OR switching OR leaving", get_sentiment=true, time=week, page=2)
Only run if {platforms} includes forums: surface churn intent on niche/product forums; use {time_window} (e.g. week) to keep results fresh and actionable.
This is exactly what the MCP returns to your agent (via the churn-intent-saver prompt or get_skill tool), with your inputs filled in.
SKILL: Churn-Intent Saver
Monitors X — and optionally Reddit and product forums — for explicit churn intent about your brand, sizes each X author's reach, and pulls context so you can intervene before they're gone — biggest megaphones first.
You are running this skill on API Direct via its MCP tools. Execute the steps below yourself by calling the named tools in order — values in <angle brackets> come from a previous step. Then deliver the result described at the end.
INPUTS:
- brand (required): <brand — ASK THE USER>
Your brand/product to monitor for churn and switching intent.
- platforms (optional): (optional — e.g. twitter, reddit, forums)
Comma-separated list of platforms to run — options: twitter, reddit, forums. Omit to run all of them; name specific platforms to limit the run.
- depth (optional): 2 (default — override if you like)
How many result pages to pull per platform (maps to each tool's pages/page param). Higher = more candidates, more cost.
- time_window (optional): week (default — override if you like)
Freshness filter for the forums sweep (maps to the forums time param). Keep recent so saves are still actionable.
PLATFORM SELECTION: some steps are gated with "Only run if {platforms} includes X". If the user supplied a `platforms` value, run only the steps whose platform is listed. If the user did NOT supply `platforms`, run ALL steps — every platform the skill supports.
STEPS:
1. Tool `search_twitter` — search_twitter(query="(cancelling OR \"switching from\" OR \"done with\") {brand}", get_sentiment=true, sort_by=most_recent, pages=2)
Core (always runs): surface explicit churn-intent posts about {brand}; keep negative-polarity ones. Use 2 to control how many pages to pull.
2. Tool `twitter_user_profile` — twitter_user_profile(username=<author>)
For each churning X author from step 1, pull followers_count and verification to size each account's blast radius.
3. Tool `twitter_user_tweets` — twitter_user_tweets(username=<author>, get_sentiment=true)
Read <author>'s recent tweets for context on why they're leaving so you can draft a tailored save.
4. Tool `search_reddit` — search_reddit(query="{brand} (cancelling OR \"switching from\" OR \"done with\")", get_sentiment=true, sort_by=most_recent, page=2)
Only run if {platforms} includes reddit: catch the same cancellation/switching intent in subreddit threads; keep negative-polarity posts and note the subreddit as added context for the save.
5. Tool `search_forums` — search_forums(query="{brand} cancel OR switching OR leaving", get_sentiment=true, time=week, page=2)
Only run if {platforms} includes forums: surface churn intent on niche/product forums; use week (e.g. week) to keep results fresh and actionable.
DELIVER: A prioritized save queue across X, Reddit and forums — handle/source, reach where available, reason, and a suggested response — highest-reach churners first.
Note: each underlying tool call is billed at its normal endpoint price; get_sentiment adds a small per-page surcharge. Page through results as needed but stop once you have enough to deliver the outcome.
Score a key B2B account's churn risk from employee posts, rival-tool job reqs, risk-event news, and public switching chatter.
Turn scattered "I wish it could" chatter across Reddit, forums, X, YouTube and Facebook into a ranked, evidence-backed feature backlog
Detect an incident from a corroborated cross-platform complaint surge minutes before the support queue floods