Skip to main content
Glama
Sign In
X MCP Server

X MCP Server

by siddheshutd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tweet-thread

Post a series of tweets as a connected thread on X. Provide an array of tweet texts to create a threaded conversation.

Instructions

Post a thread of tweets

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tweets": "<tweets>"
    },
    "name": "tweet-thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
tweetsYesAn array of tweets to post as a thread

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as whether tweets are posted sequentially, error handling, or link between tweets. Minimal transparency.

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

Conciseness3/5

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

The description is a single sentence, which is concise. However, it is too brief and lacks any structure to efficiently convey key information. It is adequately sized but under-specified.

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?

Given the number of sibling tools for posting, the description needs more context to be complete. It does not explain threading behavior, return values (no output schema), or edge cases. Incomplete for an agent to use correctly among alternatives.

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% (the only parameter 'tweets' has a description: 'An array of tweets to post as a thread'). The description adds no extra meaning beyond the schema. It does not clarify the object format or constraints, so baseline 3 is appropriate.

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?

The description clearly states 'Post a thread of tweets', specifying the verb (post) and resource (thread of tweets). It distinguishes from sibling tool 'post-tweet' which posts a single tweet. However, it could elaborate on what constitutes a thread (e.g., ordering, reply structure).

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?

No guidance is given on when to use this tool versus alternatives like 'post-tweet' for a single tweet or 'advanced-tweet'. The description lacks any context about appropriate scenarios or exclusions.

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

Deploy Server

Other Tools