No user-submitted related servers found.
Scored across 30 tools
Each tool maps to a distinct Threads API action—publishing, staging, replying, insights, search, or token management—and the descriptions call out exactly where boundaries lie. The reply-related tools in particular are carefully separated by depth, scope, and ownership, so an agent is unlikely to pick the wrong one.
The vast majority of tools follow a clear snake_case verb_noun pattern like create_post, get_replies, and hide_reply. The few exceptions—whoami, repost, reply_to—are still readable and do not break the overall predictability.
At 30 tools, this is above the 25+ threshold that makes a toolset feel heavy, even though each tool appears to cover a distinct part of the Threads API. The broad scope explains the count, but it is still more than most agents will need to hold in context at once.
The surface covers the Threads content lifecycle completely: staging, publishing, threading, carousels, quoting, replying, reposting, deleting, reply moderation, insights, search, and token refresh. There are no obvious dead ends—the missing edit operation is an API limitation, not a gap in this server.