Get engagement metrics for a tweet on X (Twitter). Returns impressions, likes, retweets, replies, quotes, and bookmarks. Use when the user asks "how did my post do?", "check my tweet analytics", or to evaluate content performance.
Connector
306,549 tools. Last updated 2026-07-25 13:02
"How to reply to a tweet on Twitter" matching MCP tools:
- Fetch the latest replies for a single X (Twitter) post by its numeric tweet id. Returns a timeline of reply tweets with text, engagement counts, author info, media, and in-reply-to metadata. Use cursor from next_cursor to fetch the next page. Cost = 4 tokens.Connector
- Reply to a company's response on a proposal. Use this for back-and-forth negotiation. After replying, the proposal status resets to 'pending' so the company sees the new message. IMPORTANT: After creating a proposal, use get_my_proposals to check if the company has responded. If status is 'responded', read the companyResponse field and relay it to the user. If the user wants to reply, use this tool. Args: api_key: Your agent API key (starts with 'bzcl_sk_') proposal_id: The UUID of the proposal to reply to message: The reply message from the customer Returns: Updated proposal with new status.Connector
- Draft a customer-facing reply to ONE review in a chosen tone (professional | friendly | apologetic | concise, default professional). Input: review text up to 10,000 chars, optional 0-5 rating for context. Returns the reply text and tone. METERED: costs 1 AU + 1 AU per 4,000 input chars (~1 AU for a short review). Every result reports its au_cost. If you also need sentiment/topics for the same review, call analyze_review with options.suggest_reply instead of calling both tools.Connector
- Post a new comment on any target in a workspace: a row, a cell, a doc text range, an html element, an entire surface, or the workspace itself. Polymorphic target shape mirrors the REST POST /api/workspaces/:slug/comments. For threading, pass `parentId` to hang the new comment as a reply (the server flattens nested replies to single depth and auto-unresolves a resolved parent). Mentions are an array of `{ kind: 'user'|'agent', id, label }` triples; the server validates each mention's access to the workspace before accepting. Fires `comment.added` (and `comment.unresolved` when a reply reopens a resolved parent). For replies to existing comments where you don't want to reconstruct the target, prefer `reply_to_comment` which derives the target from the parent. Editor or commenter role required.Connector
- Sends a reply to the customer on an existing ticket and DELIVERS it immediately (customer email plus any connected chat threads) — this is not a draft and reaches the customer. Use this once you have a final, customer-ready answer; to instead queue a reply for human approval, use the draft tool. Requires a "send"-tier credential (a draft-tier credential is refused) and the ticket must already have a customer email on file or the call is rejected. [$0.06 draft / live when trusted]Connector
Matching MCP Servers
- -license-quality-maintenanceA minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.Last updated
- Alicense-qualityCmaintenanceAI-powered MCP server for file renaming, organization, and PDF splitting using natural language prompts and content analysis.Last updated4MIT
Matching MCP Connectors
Scrape real tweets from X (Twitter) by keyword, hashtag, profile, advanced search, URL, or thread. Clean structured JSON, no official X API key, pay only per unique tweet delivered.
Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.
- Attach a root (non-reply) comment to a page, anchored to a specific passage by a {prefix, exact, suffix} text triplet so it stays pinned to the right spot as the page changes (editor+). Pass idempotency_key to make retries safe (a repeat returns the original comment instead of posting a duplicate). Use for feedback ON page content; to report problems with tela itself use submit_feedback.Connector
- Post-publish stage — reply to a buyer/inquiry message (POST /messages/reply). Sends a real message and queues a real email notification to the recipient, so the text you send is final — treat this as a live send, not a draft. ALWAYS improve the user's drafted reply before sending: fix grammar, spelling, punctuation, capitalization, and formatting, and tighten wording for a clear, professional tone — while preserving their meaning and intent. Send the corrected version, never the raw draft. When the user says "reply saying X", treat X as a rough draft to polish, not literal text to send verbatim. Requires ``to_user_id`` (the counterparty), ``message``, and ``access_token``. For a threaded reply pass the original ``thread`` verbatim and omit ``subject`` (the server prefixes "Re: <original subject>"). To find ``to_user_id``, open the conversation with `beycome_messages` and take the participant id that is not the signed-in owner. Success is 201 with ``data.id`` set to the new message id. Failures come back as 400 with a plain message: "User not found." (bad ``to_user_id``), "You cannot send a message to yourself." (``to_user_id`` is the sender), or "Invalid parameters" (e.g. empty/over-long ``message``). A 401 means the token is no longer valid — re-authenticate with `beycome_signin_start` then `beycome_signin_verify`.Connector
- Send a public reply to a support-inbox conversation, as the connected member, and return the result — it goes to the end-user on the conversation's channel. A write. Resolve conversation_id via list_conversations; read the thread with get_conversation before replying. conversation_id and body are required. For an internal-only note use add_note; to close it use resolve_conversation.Connector
- Create or update a comment on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. If `id` is provided, updates the existing comment; otherwise creates a new one. To start a new thread, pass `body` and exactly one of `issueId`, `projectId`, `initiativeId`, `documentId`, `milestoneId`, or `statusUpdateId` — comments on issues/projects/initiatives become top-level discussion threads; comments on documents/milestones become description comments. A status update holds a single thread, so a comment on an update that already has one is added to it as a reply. To reply to an existing thread, pass `parentId` and `body`; the reply inherits the parent's thread type, so no entity reference is needed. Parent reference fields are ignored when `id` or `parentId` is provided (`statusUpdateType` is rejected instead).Connector
- Add or remove an emoji reaction to a comment. Reactions are per-principal: each (commentId, principalId, emoji) combination is unique. `action: 'add'` is idempotent (re-adding the same emoji is a no-op); `action: 'remove'` deletes the row if present. Fires `comment.reaction_added` / `comment.reaction_removed`. Use this for lightweight agent acknowledgement (👍 on a request before reading, 👀 to mark in-progress, ✅ when done), cheaper than a full reply.Connector
- The Agora's one paid action: pay tiny x402 postage to DELIVER a PRIVATE direct message into another agent's inbox. Everything conversational is FREE (browse, post, reply in public threads, read your inbox); you pay only for private, targeted reach (the postage is what makes a private message get read, not spam-filtered). If a public answer works, use the free aicom_agora_reply instead. This returns the QUOTE only (price, asset, network, how to send); to actually send, GET /agora/message for a nonce then POST /agora/message with {nonce, signal_id|to, body}.Connector
- How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.Connector
- Leave a plain-text message for kapoost. Fire-and-forget: kapoost reads the inbox on his own schedule, no ETA. To make the message actionable, ALWAYS include `context` (what triggered this, which piece, which task) and — if you want a reply — `contact` (email, URL, MCP endpoint). Without a contact the message stays as an anonymous note. Do NOT claim in the message body that kapoost 'will reply' or 'has been notified' — say only what you know. For questions that require a reply, prefer `ask_human` (returns a poll ID).Connector
- Get the threaded reply to a sent email — the canonical 'did they reply yet?' call. Pass the sent email's id (from a sendEmail response). With wait=true it long-polls up to wait_timeout_ms for the reply to arrive (synchronous agent-to-agent chat); with wait=false (default) it returns immediately with the reply if one has arrived, else reply=null. Matches on the reply's threading, not a from/subject guess.Connector
- OPERATOR-ONLY. Persist the host LLM's per-ticker direction verdicts from a `direction_review_batch`. `verdicts` is a list, one entry per tweet: [{"tweet_id": "...", "verdicts": [ {"ticker": "NVDA", "is_call": true, "direction": "bullish|bearish|neutral", "confidence": 0.0-1.0, "conviction": "low|medium|high", "rationale": "..."}]}] For each (tweet_id, ticker) it marks the tweet reviewed (llm_call_cache) and upserts analyst_calls with extraction='llm' + confidence/conviction, overriding the heuristic row. Idempotent. Returns {written, is_call_1, flips_from_heuristic, tweets_newly_reviewed, rejected, errors}.Connector
- Ask the human a question on WhatsApp and BLOCK until they reply (or timeout). `text` is the question. `buttons` (optional, up to 3) render as tappable reply buttons; omit them to invite a free-text answer the human types on their phone — use this to let the human steer you mid-task. `timeout` is seconds to wait (max 90). Returns the human's reply (free text and/or the chosen option). On timeout, returns a note — the question was delivered and the answer is still retrievable via `check_replies`.Connector
- Check whether a file hash (MD5 or SHA-256) appears in the TweetFeed corpus. Exact match over the past 365 days (falls back to a 30-day window if there's no exact hit). Useful for confirming if a binary sample has been shared by the public infosec Twitter/X community. Hash type auto-detected from length (32 hex = MD5, 64 hex = SHA-256). Exact match on hex value, case-insensitive throughout.Connector
- Return the connected user's ProductClank credit balance and plan. Use before launching a campaign to confirm they have enough credits (a content campaign costs 1000; a reply boost 200; likes/reposts 300).Connector
- [Read] Aggregate per-coin social sentiment for a time range: overall sentiment, positive/negative split, mention count, and sample tweets. X/Twitter post search or tweet-level evidence -> search_x. Multi-platform social thread search -> search_ugc.Connector