Skip to main content
Glama
650,555 tools. Updated 2026-10-14 11:19

"How to publish messages on X (formerly Twitter)" matching MCP tools:

  • Identify what an X (formerly Twitter) URL points at before fetching it. Give any x.com or twitter.com URL (mobile links, query params, /i/web/status forms are fine); get back {type: profile|tweet, id, handle, canonical_url}. Tweet URLs yield the numeric id for x_get_tweet; profile URLs yield the handle for x_get_profile or x_get_tweets. Costs 2 credits and parses offline without fetching the page. t.co short links cannot be expanded offline and return INVALID_INPUT telling you so; expand them in your own browser step first. Skip this tool when you already have a handle or tweet id: the other X tools accept those directly.
    ConnectorOAuth
  • Reads and sets the SOCIAL MEDIA LINKS on a Google Business Profile: Instagram, Facebook, X (Twitter), LinkedIn, YouTube, TikTok, Pinterest, WhatsApp and the appointment link. Call with `location` alone to READ what is currently published. WHY A SEPARATE TOOL: these live in the location's ATTRIBUTES resource, not in the location body, so gbp_update_location cannot see or change them. `links` = comma-separated `network=url` pairs, e.g. `instagram=https://instagram.com/acme, youtube=https://youtube.com/@acme`. Accepted network names: instagram, facebook, twitter (or x), linkedin, youtube, tiktok, pinterest, whatsapp, appointment. `remove` = comma-separated network names to clear. Only the networks you name are touched; every other attribute on the listing is preserved. Google allows a different attribute set per business CATEGORY, so each network you pass is checked against what Google permits for that listing first and an unsupported one is reported instead of being silently dropped. confirm=false → preview of the exact before/after.
    Connector
    Destructive
    OAuth
  • Search a single network for posts matching a query, returned as the unified Post[] schema and tagged with its platform. Keyless on TikTok, YouTube, and Pinterest. Instagram, Twitter/X, Reddit, and Facebook need operator-side credentials (returns credentials_required until set). Snapchat and Threads do not support keyless search (returns not_supported); LinkedIn is quarantined. To fan one query across every network at once, use search_all.
    ConnectorNo auth
  • Returns cogDepot's public marketplace aggregate: how many agents have registered, how many deals have sealed in the recent window, and how long a deal typically takes to seal. Requires no API key, no account, and spends no credits. The figures are RECOMPUTED ON A SCHEDULE, not live. The result states when it was generated and how old that is; treat an hours- or days-old figure as the estimate it is, and never quote it as a current number. A figure cogDepot does not publish is reported as NOT STATED, which is not the same as zero. The sealed-deal count and the median are withheld until enough deals exist to publish them, so an absent figure is an absent measurement, not evidence of an empty market. This does not report how many listings are live; use cogdepot_preview_listings to see what is actually on offer. Call it to judge whether the marketplace has real activity before recommending an account.
    ConnectorNo auth
  • List chats for WhatsApp, Instagram or Telegram, most recently active first; use it to find a chat_id. LinkedIn requires inbox-specific listing. V2 filters: type, before/after (on the chat's last activity), archived and unread; WhatsApp pages by offset, other providers by cursor. For 'messages received between X and Y' call messaging_list_recent_messages, which also reads the messages.
    ConnectorOAuth
  • Publish a post to the user's LinkedIn or X account immediately. Call it once WITHOUT confirmation_token to get a preview and a token, show the user exactly what would be posted and to which account, then call it again with the token only if they agree. On X, separating blocks of text with a line containing only three dashes posts them as a chained thread.
    Connector
    Destructive
    OAuth

Matching MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    Real-time X (Twitter) data platform with 2 MCP tools covering 120+ REST API endpoints. Search tweets, look up users, get timelines, extract followers/likes/retweets in bulk, monitor accounts, run giveaway draws, and perform write actions (tweet, like, retweet, follow, DM). OAuth 2.1 authentication with PKCE.
    2
    367 npm
    213
    MIT

Matching MCP Connectors

  • X (formerly Twitter) posts, profiles, and search for AI agents. Free key, self-minted, no signup.

  • Twitter: Access real-time Twitter/X data as soon as it's posted! With the Twitter/X AIO API, you.

  • List X (Twitter) accounts connected to the authenticated Vee3 account for write capabilities. Returns user_id, user_name, display name, avatar URL, and whether each account is the default. Use user_id or user_name on future write calls, or omit both to use the default account. If accounts is empty, the user must connect an X account at https://vee3.io/dashboard/connections before write capabilities work. Agents cannot complete OAuth; ask the user to connect, then call this tool again. Cost = 0 tokens.
    ConnectorNo auth
  • Which dates a bank actually published a rate table — 'did the ECB publish on 2026-01-01?', 'how often does the US Treasury publish?'. Dates only, no values, so it is on every plan (API key required, free tier). Give `year` or a from/to range; large ranges are capped and flagged `truncated`.
    ConnectorNo auth
  • Free. Latest daily X (Twitter) sentiment score for each prediction market we track (Polymarket), with the change since the previous day, the catalyst and the market's Yes price. For a fresh score on any other question use get_market_sentiment.
    ConnectorNo auth
  • Free. Latest daily X (Twitter) sentiment score for each prediction market we track (Polymarket), with the change since the previous day, the catalyst and the market's Yes price. For a fresh score on any other question use get_market_sentiment.
    ConnectorNo auth
  • Search Twitter/X. Returns a compact human-readable list by default; pass format='json' for full structured data. Use glim_twitter_get(ref) for full thread context. Use docs://search-operators for reference.
    ConnectorNo auth
  • Comments / replies on one post as the unified Comment[] schema, tagged with its platform. Provide url OR postId. Keyless on TikTok, YouTube, and Threads (and a single tweet via syndication on Twitter/X). Instagram, Reddit, and Facebook need operator-side credentials; Snapchat comments are not supported keyless; LinkedIn is quarantined.
    ConnectorNo auth
  • List messages in a chat from LOCAL history. Requires chat_jid (from whatsapp_chats). Paginate backwards by passing the oldest message's timestamp as `before` (ISO 8601); `after` pages forward; `order` sorts. NOTE: only messages already synced locally are returned — to see how far back the archive goes use whatsapp_history_coverage, and to pull OLDER messages from your phone use whatsapp_history_backfill.
    ConnectorNo auth
  • Turn one article into an X/Twitter thread of 5-10 posts. Use when X is the only target. For LinkedIn, email, and blog versions at once, use repurpose-long-form. URLs are not fetched; paste the text. Pay-per-call: $0.05 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • Retrieve messages from YOUR inbox — the agent itself (its signature), or the owner of an owned agent (the OAuth connector's account). By DEFAULT returns only the most recent 5 messages (newest last) plus `count` = the total in the inbox — so you are never flooded. Page further back with `limit` (how many to return) and `before` (return the `limit` messages ending just before this index; omit for the newest). Set `limit: 0` to fetch the ENTIRE inbox (can be very large). Reads are never suppressed; an `unacked_standing_orders` section is attached when you have standing orders to acknowledge (ack_standing_orders). bypass_gate is accepted but a no-op. AUTH — SIGN THE REQUEST. Ed25519 over the handoff-signed-req statement, headers X-Agent-Id / X-Signature / X-Timestamp, so nothing secret crosses the wire; scripts/handoff-lib.mjs restFetch is the reference signer, and `handoff enroll <id>` mints your signing key if you have none. TRANSPORT: signing works on BOTH MCP transports — the per-POST /mcp one, and the legacy SSE bridge (GET /mcp + POST /mcp/messages), where each message POST carries its own signature (sign the path /mcp/messages WITHOUT the ?sessionId query; signatures are single-use on that channel, so sign each message rather than replaying one).
    ConnectorNo auth
  • Create a post on X/Twitter, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, or Telegram with optional media. Posts immediately or at a scheduled time. Publish to several accounts at once by naming account_ids instead of account_id, and give one of them its own text or media with account_configurations. Note: Instagram REQUIRES media. X posts whose text contains a link are billed at $0.25 each on paid plans and are rejected on the Free plan (x_link_posts_require_paid_plan); X accounts connected with your own X API keys are exempt. A spent monthly post or scheduled-post quota answers 429 usage_limit_exceeded, which waiting does not clear; the separate per-minute burst limit on the API key answers 429 rate_limited and does clear. Set draft: true to save the post without sending it: nothing reaches the platform, nothing counts against the monthly quota, the text may even be empty, and the answer carries a `warnings` array saying per account what would go wrong if it were sent as it stands. chirpie_update_post edits a draft and promotes it with schedule_at or publish: true.
    ConnectorAPI key
  • Create a thread (multiple posts) on X/Twitter, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, or Telegram. Publish to several accounts at once by naming account_ids instead of account_id, and give one of them a thread of its own with account_configurations. X, Bluesky, Threads, Mastodon, and Telegram support native reply threading. Others degrade gracefully to standalone posts. A THREAD IS ATOMIC: if any part fails, every part already published is deleted from the platform and the whole thread's quota is refunded, and the error's `thread_rollback` says what was rolled back. Two codes tell you whether a retry is safe: `upstream_error` means nothing of the thread is on the platform, so repeating the request is safe, while `thread_rollback_incomplete` means the posts named in `thread_rollback.still_live` are still up with their ids and URLs, and repeating the request would publish them twice. On an Instagram account connected by signing in with Instagram, where Chirpie cannot delete a published post, a failed thread always reports its published parts as still live. On X, each post in the thread whose text contains a link is billed at $0.25 on paid plans; on the Free plan such threads are rejected (x_link_posts_require_paid_plan). X accounts connected with your own X API keys are exempt. A thread that would cross the monthly post or scheduled-post quota answers 429 usage_limit_exceeded and publishes nothing; the per-minute burst limit on the API key answers 429 rate_limited. Set draft: true to save the thread without sending it: nothing reaches the platform, nothing counts against the quota, a draft thread may still be a single part long, and the answer carries a `warnings` array. chirpie_update_post on any of its parts promotes it, and the whole thread goes together.
    ConnectorAPI key
  • Shows what posting to X (Twitter) costs this account and what it has left. X is a pay-per-use add-on of the paid plans (Starter, Pro, Agency, Scale; not Free, not during a trial): 1 X credit = 1 plain X post, a post with a link uses 10, each image or video adds 1. Returns mode (paid, free, trial or internal), the plan's monthly X credits, used and left, top-up credits, X posts today against the daily limit, the price table, the last movements, and links to buy top-up credits (80 credits for $5, 340 for $20; each opens a Stripe payment page, nothing is charged unless paid there). With text, it also returns how many credits that post would use (with thread or reply: the whole chain).
    ConnectorNo auth
  • Move YOUR read cursor in one conversation: up to message_id, up to ts, or (neither) up to its newest message. The cursor only moves forward — an older point changes nothing. Returns read_ts and how many stay unread. MCP twin of POST /agents/:id/conversations/:cid/read. AUTH — SIGN THE REQUEST. Ed25519 over the handoff-signed-req statement, headers X-Agent-Id / X-Signature / X-Timestamp, so nothing secret crosses the wire; scripts/handoff-lib.mjs restFetch is the reference signer, and `handoff enroll <id>` mints your signing key if you have none. TRANSPORT: signing works on BOTH MCP transports — the per-POST /mcp one, and the legacy SSE bridge (GET /mcp + POST /mcp/messages), where each message POST carries its own signature (sign the path /mcp/messages WITHOUT the ?sessionId query; signatures are single-use on that channel, so sign each message rather than replaying one).
    ConnectorNo auth
  • Check whether the user's tweets can be pulled: the X (Twitter) API connection (connected / disconnected), whether the browser extension has synced recently, and a rolled-up can_pull + how (x_api or extension). Use this before a sync, or when the user asks why bookmarks aren't updating. Note: the extension is browser-only and can't be driven by an agent.
    ConnectorNo auth
  • Force-pull the user's most recent bookmarks from the X API now (server-side). Requires a connected X account; if the account only syncs via the browser extension, this reports that a browser sync is needed. Use when the user asks to refresh / fetch their latest saves. For Twitter-list freshness, use get_list_tweets instead.
    ConnectorNo auth