Skip to main content
Glama
opentweetio

OpenTweet MCP Server

Official
by opentweetio

opentweet_update_tweet

DestructiveIdempotent

Update an existing draft or scheduled tweet by modifying text, media, category, schedule, or thread settings. Cannot edit already-published tweets.

Instructions

Update an existing tweet. Can change text, category, schedule, or media. Cannot edit already-posted tweets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe tweet/post ID to update
textNoNew tweet text (max 280 chars for free X accounts, up to 25,000 for Premium+)
categoryNoNew category
is_threadNoConvert to/from thread
media_urlsNoNew media URLs (replaces existing)
community_idNoX Community ID to post to, or null to remove
thread_mediaNoMedia URLs per thread tweet (array of arrays)
thread_tweetsNoUpdated thread tweets (excluding the first tweet which is the main text)
scheduled_dateNoNew schedule date (ISO 8601), or null to unschedule
share_with_followersNoShare community post with followers too
Behavior4/5

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

Annotations already provide destructiveHint and idempotentHint. Description adds value by stating the 'cannot edit already-posted tweets' restriction, which is not in annotations.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficiently conveys core function and key limitation.

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 10 parameters with full schema coverage, description adequately summarizes editable fields. Lacks details on thread or community parameters but schema covers them.

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 baseline is 3. Description only enumerates fields (text, category, schedule, media) without adding new meaning beyond 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 states 'Update an existing tweet' with specific verbs and resources, and explicitly says 'Cannot edit already-posted tweets', distinguishing it from siblings like create, delete, publish.

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

Usage Guidelines4/5

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

Provides clear constraint 'Cannot edit already-posted tweets', guiding when not to use. Lacks explicit alternatives but contextually clear given sibling tool names.

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/opentweetio/mcp-server'

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