meta-threads-mcp
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| threads_create_postA | Create and publish a text post to Threads. Args: ctx: FastMCP request context text: The text content of the post reply_control: Who can reply - EVERYONE, ACCOUNTS_YOU_FOLLOW, or MENTIONED_ONLY |
| threads_create_image_postA | Create and publish a post with an image to Threads. Args: ctx: FastMCP request context image_url: URL of the image to post text: Optional text content of the post reply_control: Who can reply - EVERYONE, ACCOUNTS_YOU_FOLLOW, or MENTIONED_ONLY |
| threads_create_video_postA | Create and publish a post with a video to Threads. Args: ctx: FastMCP request context video_url: URL of the video to post text: Optional text content of the post reply_control: Who can reply - EVERYONE, ACCOUNTS_YOU_FOLLOW, or MENTIONED_ONLY |
| threads_get_postB | Get a Threads post by ID. Args: ctx: FastMCP request context post_id: The ID of the post to retrieve |
| threads_get_user_postsB | Get the authenticated user's recent posts. Args: ctx: FastMCP request context limit: Maximum number of posts to return (default 10) |
| threads_delete_postC | Delete a Threads post. Args: ctx: FastMCP request context post_id: The ID of the post to delete |
| threads_get_publishing_limitA | Check remaining publishing quota (250 posts/day, 1000 replies/day). Args: ctx: FastMCP request context |
| threads_reply_to_postA | Reply to an existing Threads post. Args: ctx: FastMCP request context post_id: The ID of the post to reply to text: The text content of the reply |
| threads_get_repliesB | Get replies to a Threads post. Args: ctx: FastMCP request context post_id: The ID of the post to get replies for |
| threads_get_conversationB | Get the full conversation thread for a post. Args: ctx: FastMCP request context post_id: The ID of the post to get the conversation for |
| threads_hide_replyB | Hide a reply to your post. Args: ctx: FastMCP request context reply_id: The ID of the reply to hide |
| threads_unhide_replyA | Unhide a previously hidden reply. Args: ctx: FastMCP request context reply_id: The ID of the reply to unhide |
| threads_get_media_insightsB | Get metrics/insights for a specific post. Args: ctx: FastMCP request context media_id: The ID of the media/post to get insights for |
| threads_get_user_insightsA | Get user-level metrics/insights for the authenticated user. Args: ctx: FastMCP request context |
| threads_get_profileB | Get the authenticated user's profile. Args: ctx: FastMCP request context |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| reply_strategy | Craft a thoughtful reply to a thread. Args: context: The original post or conversation context |
| content_ideas | Generate content ideas for Threads. Args: niche: Your content niche or area of expertise count: Number of ideas to generate |
| analyze_engagement | Analyze engagement metrics and suggest improvements. Args: metrics: Description of your current engagement metrics or recent post performance |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action; even the three creation variants are clearly separated by media type. The only subtle overlap is between get_replies and get_conversation, but their descriptions differentiate direct replies from a full threaded view.
All tools follow a consistent pattern: prefixed with `threads_` followed by a verb and noun (e.g., create_post, get_replies, hide_reply). No mixed naming conventions, making the set predictable.
15 tools is appropriately scoped for a social media API server, covering content creation, retrieval, deletion, replies, moderation, and analytics without feeling bloated.
Core content lifecycle (create/get/delete/reply) is covered along with moderation (hide/unhide) and analytics for both media and user. Some gaps exist such as searching posts or accessing other users' profiles, but these are beyond the typical API scope, so overall this is a solid surface.