Social Media Hashtag Research avatar
Social Media Hashtag Research

Pricing

Pay per usage

Go to Store
Social Media Hashtag Research

Social Media Hashtag Research

Developed by

Apify

Apify

Maintained by Apify

Extract information about posts across social media with the same hashtag. Get details from Instagram, YouTube, TikTok, and Facebook about posts’ URLs, captions, timestamps, likes, dislikes, views and comments count, and basic profile info. You can download your data in JSON, CSV, Excel, and more.

4.1 (4)

Pricing

Pay per usage

53

Total users

1.1K

Monthly users

106

Runs succeeded

>99%

Issues response

87 days

Last modified

3 months ago

You can access the Social Media Hashtag Research programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"apify/social-media-hashtag-research"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with Social Media Hashtag Research

You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:

{
"mcpServers": {
"remote-actors-mcp-server": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=apify/social-media-hashtag-research",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.