Skip to main content
Glama

post_tweet

Post a text-only tweet (max 280 characters) to Twitter/X. Optionally reply to a specific tweet by including its ID.

Instructions

Posts a new text-only tweet to the authenticated Twitter/X account. Use this tool when the LLM needs to publish a status update, share information, announce something, or reply to an existing tweet in a thread. The tweet text must be 280 characters or fewer. Optionally accepts a reply_to_tweet_id to post as a threaded reply. Returns the created tweet ID, full text, author identifier, and creation timestamp. Prefer this over post_tweet_with_image when no media attachment is needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe main body text of the tweet. Maximum 280 characters. Supports Unicode, emoji, hashtags (#), mentions (@), and URLs. The text will be posted verbatim to Twitter as a new status update.
reply_to_tweet_idNoThe unique numeric ID of an existing tweet to reply to. When provided, the new tweet will be posted as a threaded reply directly beneath the specified parent tweet. Omit this field to post a top-level (non-reply) tweet.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesIndicates the outcome of the operation: "success" or "error".
messageYesA human-readable summary of the result, e.g. "Tweet posted successfully".
dataYesContainer holding the created tweet details.
Behavior4/5

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

No annotations are provided, so the description fully carries the burden. It discloses the 280-character limit, optional reply parameter, and return fields. However, it does not mention authentication requirements, rate limits, or any potential side effects beyond posting.

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 paragraph of five sentences, starting with the core purpose. Every sentence adds necessary information without redundancy, making it concise and well-structured.

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

Completeness4/5

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

Given the low complexity (2 params, 1 required, output schema exists), the description covers purpose, usage, parameters, and return values adequately. It lacks error handling or rate limit info, but for a simple post tool, this is sufficient.

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 input schema already documents both parameters well. The description adds value by explaining that it's text-only and clarifying the reply function, but does not significantly augment the schema's meaning.

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 it posts a text-only tweet to the authenticated account. It distinguishes itself from the sibling tool "post_tweet_with_image" by explicitly stating preference when no media attachment is needed.

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

Usage Guidelines5/5

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

The description explains when to use the tool (publish status updates, share info, announce, reply) and explicitly names an alternative (post_tweet_with_image) for when media is needed. Provides clear context for usage.

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/GenAIwithMS/twitter-mcp'

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