Thread Analyzer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_threadA | Scrape replies from a public Threads post URL. Opens a browser, navigates to the post, intercepts GraphQL API responses to extract replies, and saves them locally. This must be called before using get_all_replies or search_replies. Args: url: Full URL of the Threads post (e.g. https://www.threads.com/@user/post/ABC123) max_scrolls: Maximum scroll iterations for loading more replies (default: 20) |
| get_all_repliesA | Get all scraped Threads replies. Returns a formatted list of all replies with username, timestamp and text. Call scrape_thread first if no data exists yet. |
| search_repliesA | Search Threads replies for a keyword (case-insensitive). Args: keyword: The search term to filter replies by. Returns matching replies with username and text. |
| get_reply_statsA | Get statistics about the scraped replies. Returns reply count, unique users, most active commenters, and time range of replies. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct role: scrape_thread for fetching, get_all_replies for retrieving all, search_replies for filtering, get_reply_stats for analytics. No overlap or ambiguity.
All tools follow a clear verb_noun snake_case pattern (scrape_, get_, search_), making the API predictable and easy to navigate.
Four tools is well-scoped for a focused Threads analysis server, covering the full workflow without bloat or missing essentials.
The tool surface covers scraping, retrieval, search, and stats—everything needed for the stated purpose of analyzing Threads replies. No obvious gaps.