X Profile Reactions

Give it an X profile, get back its posts with the reaction counts each one drew.

What it does

• Scrapes an X profile’s posts together with the reactions each post drew — likes, retweets, replies and views.
• Returns per-post totals, not the list of accounts that reacted. You get the number 214, not the 214 handles behind it.
• Adds filters the plain post tool does not have: date range, sort order, extra handles, and search terms.
• sort accepts "Top", "Latest" or "Latest + Top". Default is "Top".
• twitter_handles lets you add more handles to the same run. search_terms narrows what is collected, and include_search_terms controls whether those terms are applied.

Use cases

• Find the posts worth mining. Per-post totals show which of an account’s posts drew a crowd before you spend on pulling commenters.
• Benchmark content performance. Compare handles to see whose message the market actually responds to.
• Window an analysis by date. Date filters isolate a launch or campaign period rather than the whole timeline.
• Prioritise a research budget. Rank posts by engagement, then run x_post_commenters on only the top ones.

How to use it

Get reactions for the X profile https://x.com/janedoe, sorted by Top,
max 20 posts. Which posts got the most engagement?

Pull reactions for https://x.com/stripe between 2026-06-01 and 2026-07-31,
sorted by Latest.

Run reactions for https://x.com/janedoe and also include handles stripe and
ramp. Rank all posts by likes.

Example prompts

Best prompting practices

• Say “reaction counts”, not “who reacted”. The second phrasing sets an expectation this tool cannot meet.
• Pass a full profile_url. A bare handle is not enough here — profile_url is required.
• Set a date range when you are researching a specific campaign or launch. start_date and end_date are YYYY-MM-DD; “during the launch” will not parse. Without them you get whatever the sort order surfaces.
• Use "Latest" for recency, "Top" for signal. "Top" is the default and is usually what you want before writing outreach.
• Narrow with search_terms when the account posts about more than the thing you care about — it collects on topic rather than on everything.
• Batch the extra handles. twitter_handles folds several accounts into one call instead of one call each.
• Ask for the numbers per post. Post text, date, URL, likes, retweets, replies, views — the engagement figures are the point of this tool, and they are the first thing a summary drops.
• Set max_posts to what you will read. Default is 10, ceiling is 100, and billing is per post returned.

Output

{
  "profile_url": "https://x.com/janedoe",
  "posts": [
    {
      "text": "We just shipped self-serve onboarding.",
      "likes": 214,
      "retweets": 31,
      "replies": 18,
      "views": 12400
    }
  ]
}

Credits and limits

0.3 credits per post returned. max_posts accepts 1–100 and defaults to 10, so a default call costs up to 3 credits and a full 100-post call up to 30. Run check_credits (free) before a large batch.

Parameters

Related tools

Next steps

• All MCP tools — the full catalogue with credit costs
• AI for Sales Reps — workflows that chain this tool into outreach research

Keep learning

Two courses take these tools past the reference page — clustered by GTM job, then chained into workflows.