Skip to main content
Glama
Sign In
X MCP Server

X MCP Server

by siddheshutd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

advanced-tweet

Post tweets with advanced options: reply to an existing tweet, quote a tweet, or create a poll.

Instructions

Post a tweet with advanced options like reply to a tweet, quote a specific tweet, or create a poll for the tweet,

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": {
      "text": "<text>"
    },
    "name": "advanced-tweet"
  }
}

Input Schema

NameRequiredDescriptionDefault
pollNoAdd a poll to the tweet
textYesThe text content of the tweet
quoteNoTweet ID to quote
reply_toNoTweet ID to reply to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description indicates a write operation ('Post a tweet') which is inherently non-destructive for new content, but it does not mention rate limits, permissions, or return behavior. The description is adequate but not rich.

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

Conciseness5/5

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

The description is a single sentence that efficiently conveys the tool's purpose. It is front-loaded with the core action and lists key features concisely, with no redundant information.

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 tool has 4 parameters, a nested object, and no output schema, the description lacks completeness. It does not mention constraints like text length, poll option limits (though present in schema), or what the response looks like, and fails to guide the agent on when to choose this over sibling tools like 'post-tweet'.

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%, so the schema already describes each parameter. The description adds context by grouping the advanced options (reply, quote, poll) but does not provide additional meaning beyond the schema descriptions.

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

Purpose5/5

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

The description clearly states the tool posts a tweet with advanced features, listing reply, quote, and poll. It uses a specific verb 'Post' and resource 'tweet' with distinct capabilities, distinguishing it from basic posting tools like 'post-tweet'.

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

Usage Guidelines3/5

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

The description implies use when advanced options are needed but does not explicitly state when to use this tool versus simpler alternatives like 'post-tweet' or 'quote-a-tweet'. No exclusions or prerequisites are provided.

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