Skip to main content
Glama
angheljf

social-media-mcp

create_x_thread

Create and publish threaded posts on X (formerly Twitter) to share extended content through connected messages.

Instructions

Create a thread on X (formerly Twitter)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesContent of the first post

Implementation Reference

  • The implementation of the create_x_thread tool, which posts content to Twitter/X via the twitterClient.
    else if (request.params.name === "create_x_thread") {
        if (!isValidPostArgs(request.params.arguments)) {
               throw new McpError(
                   ErrorCode.InvalidParams,
                   "Invalid post arguments"
                );
        }
           const { content } = request.params.arguments;
           try {
               await sleep(2000)
                   const tweet = await twitterClient.v2.tweet(content)
               const threadId = tweet.data.id;
               const newPost: SocialMediaPost = {
                   content,
                   platform: "X",
                   timestamp: new Date().toISOString(),
                   threadId: threadId,
                   tweetId: tweet.data.id
               };
               this.socialMediaPosts.push(newPost);
               return {
                   content: [
                       {
                           type: "text",
                          text: `Successfully created X thread: ${content}. Thread ID: ${threadId}`,
                      },
                   ],
              };
          } catch (error: any) {
               return {
                   isError: true,
                   content: [
                       {
                           type: "text",
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry full behavioral disclosure burden. It only states that creation happens, but omits critical mutation details: authentication requirements, rate limits, character limits, whether the operation is idempotent, or what happens if the API fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief single sentence with no redundant words. However, the brevity trades off against necessary behavioral disclosure for a social media posting tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Insufficient for a write-operation tool. Missing: output behavior (does it return the thread ID?), mechanism for adding subsequent posts (since it only accepts 'first post' content), error conditions specific to X API, and safety considerations. The 'formerly Twitter' clarification is helpful but doesn't compensate for missing operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear parameter descriptions ('Content of the first post'). The description adds no additional parameter context (e.g., expected format, length constraints, that this only creates the first post), meeting the baseline for well-schematized tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific action (Create) and resource (thread on X/Twitter). However, it does not explicitly differentiate from sibling `post_to_x`, leaving ambiguity about when to use the thread creator versus a single post tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this tool versus the sibling `post_to_x` or `list_x_posts`. No prerequisites, conditions, or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/angheljf/social-media-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server