threads-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THREADS_USER_ID | No | Your Threads user ID. Optional: skips the initial GET /me call to fetch your user ID. | |
| THREADS_ACCESS_TOKEN | Yes | Your Threads API access token. Required for authentication. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileB | Get the authenticated user's Threads profile information |
| get_publishing_limitB | Get the current publishing quota usage and limits for the authenticated user |
| get_account_insightsB | Get insights/analytics for the authenticated user's Threads account |
| list_my_threadsB | List all Threads posts by the authenticated user |
| list_my_repliesB | List all replies made by the authenticated user |
| get_threadB | Get details of a specific Threads post by ID |
| get_thread_insightsC | Get engagement insights for a specific Threads post |
| get_mentionsA | Get threads where the authenticated user has been @mentioned |
| create_text_postA | Create a text-only Threads post. Set publish:true to immediately publish, or false to get a container_id for later publishing. |
| create_image_postC | Create a Threads post with an image. Set publish:true to immediately publish. |
| create_video_postA | Create a Threads post with a video. Videos require processing time — use get_container_status to check readiness, then publish_thread when FINISHED. |
| create_carousel_postA | Create a carousel post with multiple images or videos. Set publish:true to immediately publish after container creation. |
| publish_threadA | Publish a previously created media container. Use after create_*_post with publish:false, or after a video finishes processing. |
| get_container_statusB | Check the processing status of a media container (useful for videos) |
| delete_threadB | Delete a Threads post by ID |
| repost_threadB | Repost (share) a Threads post from another user |
| quote_threadB | Create a quote post that references another thread |
| get_repliesC | Get direct replies to a specific Threads post |
| get_conversationA | Get the full conversation thread (all replies at any level) for a Threads post |
| reply_to_threadA | Post a reply to a Threads post. Creates and immediately publishes a text reply. |
| manage_replyB | Hide or unhide a reply on the authenticated user's threads |
| search_keywordB | Search Threads posts by keyword. Requires threads_keyword_search permission. |
| lookup_profileA | Look up a Threads user profile by username. Requires threads_profile_discovery permission. |
| list_profile_postsC | List public Threads posts from a specific user by their user ID |
| search_locationsA | Search for location tags that can be attached to Threads posts |
| get_locationA | Get details about a specific location tag by its ID |
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 26 tools
Each tool targets a distinct action and resource, with clear descriptions that differentiate overlapping concepts like get_thread vs get_conversation vs get_replies. No two tools are easily confused.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_text_post, get_thread_insights). No mixing of styles or ambiguous verbs.
With 26 tools, the set is on the higher end but each tool serves a specific and necessary function for the Threads API, covering posting, reading, searching, analytics, and moderation without unnecessary redundancy.
The tool surface covers core CRUD and lifecycle operations for posts, plus searching and analytics. A notable gap is the lack of an update/edit tool for posts, but most workflows are supported.