Skip to Content
MCPToolsX Post Commenters

X Post Commenters

Give it an X (Twitter) post URL, get back the accounts that commented on it.

Tool
x_post_commenters
Cost
0.4 credits
Category
X (Twitter)
Required input
post_url
Returns
Accounts that commented on the post

What it does

  • Returns the accounts that commented on an X post.
  • One call, not pages — set max_results between 1 and 1000. Default is 100.
  • Useful for building warm lead lists from an engaged audience: people who replied to a post about your problem space already care about it.
  • Returns X accounts, not LinkedIn profiles. There is no email in the response.

This gives you handles. To reach a work inbox you need a LinkedIn profile first — match the person with find_people, then run find_work_email.


Parameters

ParameterTypeRequiredNotes
post_urlstringYesFull X post URL
max_resultsnumberNo1–1000, default 100

How to use it

Connect the MCP server

Follow the setup guide for your client. Browser sign-in, no API key.

Find the post

Get the recent posts from @stripe and show me the ones about revenue operations with the most replies.

Pull the commenters

Get the commenters on that X post. 500 results.

Filter to real prospects

Drop accounts with no bio, no company and fewer than 50 followers. Keep the ones whose bio names a job title.

Cross over to LinkedIn

For the accounts that survived, search for a matching LinkedIn profile by name and company. Only keep confident matches.

Example prompts

Ask your clientWhat you get back
”Who commented on this X post?”Commenting accounts with their comment text
”Commenters on this post, 500 max”A larger single-call pull
”Commenters, keep only bios that mention a company”A filtered warm list
”Find posts from this profile first, then their commenters”Chains x_profile_posts — 0.4 credits

Best prompting practices

  • Set max_results deliberately. The default of 100 truncates a busy thread; 1000 on a quiet one just returns everything available.
  • Filter on the bio. X bios are the only firmographic signal in the response. No bio usually means no usable prospect.
  • Do not expect emails. This tool returns social accounts. Any email has to come from a separate enrichment step.
  • Pick topic posts over brand posts. A reply to “here is how we forecast” beats a reply to a product announcement.
  • Batch by post, not by account. One call covers a whole thread — there is no reason to run it per person.

Output

{ "commenters": [ { "username": "janedoe", "name": "Jane Doe", "bio": "VP RevOps", "comment": "We hit exactly this problem last quarter." } ] }

Credits and limits

0.4 credits per call, flat, whatever max_results you set. Maximum 1000 commenters per call. Run check_credits (free) before working through a list of posts.

A high max_results does not create commenters that are not there. If a thread has 40 replies, asking for 1000 returns 40 and costs the same 0.4 credits.


ToolUse it instead when
x_profile_reactionsYou want one profile’s posts with per-post reaction totals rather than the accounts that reacted — 0.2 credits
x_profile_postsYou need the post URLs first — 0.4 credits
linkedin_post_commentersYou want the same play on LinkedIn, where profiles carry job titles — 0.3 credits
tiktok_comments_from_postYou want the same play on TikTok — 0.3 credits

Next steps


Keep learning

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