Skip to main content
Glama
getxapi

getxapi-mcp

Official

create_tweet

Post tweets to X with text, images, and videos. Supports replies, quote tweets, and community posts.

Instructions

Post tweets with text, images, and videos via API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesTweet text.
mediaNoBase64-encoded media — uploaded automatically.
media_idsNoPre-uploaded media ids.
media_urlsNoURLs to images/videos — fetched and uploaded automatically.
community_idNoNumeric community ID. Posts the tweet to a community the auth_token's user is already a member of. Non-members get 403. Communities with moderator review return HTTP 202 with `pending_moderation: true` (no tweet ID issued until approved). Both short and long-form (Premium) community posts are supported.
quote_tweet_idNoTweet ID to quote — resolved to URL automatically (use `quote_tweet_url` for faster requests).
verify_premiumNoWhen true and a long video (>2:20) is detected in the upload, the server verifies the auth_token's account is on X Premium before proceeding. Returns 403 if not. The duration is auto-detected from the MP4 header — no extra fields needed.
quote_tweet_urlNoFull URL of the tweet to quote (e.g. `https://x.com/username/status/123456`).
reply_to_tweet_idNoTweet id being replied to.
Behavior2/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true, but the description adds minimal behavioral context (e.g., no mention of rate limits, authentication, or character limits). The 'via API' phrase is vague.

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?

The description is a single sentence that efficiently conveys the core purpose, with no redundancy. It is front-loaded but could include more detail without becoming verbose.

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?

Despite 9 parameters and no output schema, the description is too minimal. It does not address return values, error handling, or media constraints, making it incomplete for a complex creation tool.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no extra meaning beyond what the schema provides, earning a baseline score of 3.

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 tweets with text, images, and videos via API, distinguishing it from sibling tools like delete_tweet or get_tweet_detail.

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 on when to use this tool versus alternatives. The description lacks exclusions or context for choosing create_tweet over other write tools like send_direct_message or retweet.

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/getxapi/getxapi-mcp'

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