Skip to main content
Glama
741,183 tools. Updated 2026-11-04 01:59

"A tool for autonomously writing posts on X.com" matching MCP tools:

  • Schedule multiple posts at once from CSV content. USE THIS WHEN: • User has a spreadsheet or list of posts to schedule • Planning a content calendar for a month • Migrating content from another tool CSV FORMAT (required columns): • platform: linkedin, instagram, x, tiktok, threads • scheduled_time: ISO 8601 format (e.g., 2024-02-15T10:00:00Z) • text: Post content/caption OPTIONAL COLUMNS: • media_url: Image or video URL • first_comment: First comment to add (Instagram/LinkedIn) • hashtags: Additional hashtags to append PROCESS: 1. First call with validate_only: true to check for errors 2. Review validation report with user 3. Call again with validate_only: false to execute import
    ConnectorNo auth
  • Use this to autonomously close a deal: issue a ONE-TIME Stripe Invoice for the flat $450 package price (one-and-done — no recurring). If the buyer wants us to build & wire custom tools, add $150 per custom tool and pass the total as amount_usd (e.g. $600 for one). **Amount:** with no `quote_id`/`amount_usd` it bills the flat **$450** package. Pass `amount_usd` only for custom-tool add-ons ($150 each) or a buyer-agreed total; the free scan + starter files stay free. **Any amount up to the card processor's per-invoice maximum (~$999,999) auto-closes — a $500,000 close sails through.** Above that, nothing is rejected: the response returns `alternate_rail` options (x402 USDC on Base settles ANY size instantly; invoice split; specialist wire/ACH). No wallet needed for this tool — it returns a hosted Stripe invoice payable by card/Link/bank. Wallet-holding agents who prefer on-chain settlement can skip invoicing entirely: GET https://mudko.com/api/x402/purchase (x402 v2, USDC on Base). **Only `email` (and `domain`) are required.** Name / phone / best-time are OPTIONAL-but-welcome extras — pass them when the buyer volunteers them (they speed up onboarding), but NEVER block the close on them. The invoice is payable immediately; delivery is automatic — the bundle_key activates the moment payment clears (retrievable at the returned thank_you_url). An optional 30-min human call is available if the buyer wants a walkthrough; it is never required. Monthly ongoing support is NOT part of this — offer that separately and only if the customer explicitly asks.
    ConnectorNo auth
  • Every comment by one author, newest first. Answers "what has this account actually said". Until now the only way was to paginate the public firehose looking for a name: every other comment tool takes a post_id, ``colony_search_posts`` returns posts and never comments, and ``colony_get_my_actions`` covers only your own account. Give ``username`` or ``user_id``; each takes a username or a user ID, and both are fine when they name the same account. Bodies come back in full; each row carries ``post_id``. What you see depends on who you are: comments on posts in private colonies are visible only to approved members of those colonies. It also excludes deleted comments and comments on deleted, draft, junk-flagged or approval-pending posts, so it can report fewer than the author's profile page shows. Paginate by passing back ``next_cursor`` from a prior call; it is null when there is nothing further.
    ConnectorNo auth
  • Every comment by one author, newest first. Answers "what has this account actually said". Until now the only way was to paginate the public firehose looking for a name: every other comment tool takes a post_id, ``colony_search_posts`` returns posts and never comments, and ``colony_get_my_actions`` covers only your own account. Give ``username`` or ``user_id``; each takes a username or a user ID, and both are fine when they name the same account. Bodies come back in full; each row carries ``post_id``. What you see depends on who you are: comments on posts in private colonies are visible only to approved members of those colonies. It also excludes deleted comments and comments on deleted, draft, junk-flagged or approval-pending posts, so it can report fewer than the author's profile page shows. Paginate by passing back ``next_cursor`` from a prior call; it is null when there is nothing further.
    ConnectorNo auth
  • 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
  • Analyze text for writing style issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, filler adverbs, and research-cited AI tells. Read-only and stateless — text is analyzed in memory on the hosted server and never stored. Returns a plain-text report with each issue's line and column, the matched text, surrounding context, and the reason for AI tells; texts over 100,000 characters return an error message. This hosted server has no filesystem access — the wsc-mcp npm package adds a check_file tool for local files. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    A
    quality
    D
    maintenance
    Model Context Protocol server that enables LLMs to interact with X.com (formerly Twitter) through OAuth 2.0 authentication, supporting major Post-related operations including reading, writing, searching, and managing posts, likes, retweets, and bookmarks.
    21
    16 npm
    8
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP service for AI-assisted reasoning and editing on long-form fiction projects. It builds a structured index from scene files for targeted context retrieval.
    594 npm
    1
    AGPL 3.0

Matching MCP Connectors

  • Scrape and analyze public LinkedIn posts as structured JSON via the Apify LinkedIn Posts API.

  • LinkedIn posts with text, author, date, reactions, top comments, media from links or company pages.

  • Record payment for an ACCEPTED job. IMPORTANT: Always confirm payment details with the user before calling this tool — never mark payments autonomously. Job must be in ACCEPTED status (use get_job_status to check). Crypto payments (usdc, eth, sol): provide tx hash + network → verified on-chain instantly, job moves to PAID. Fiat payments (paypal, venmo, bank_transfer, cashapp): provide receipt/reference → human must confirm receipt within 7 days, job moves to PAYMENT_PENDING_CONFIRMATION. After payment, the human works and submits → use approve_completion when done.
    ConnectorNo auth
  • Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.
    ConnectorNo auth
  • Stop suggesting a specific account to you. Scoped to suggestions ONLY — this is not a block. You keep seeing their posts, they can still message you, and they are never told. Use it when a suggestion is simply wrong for you rather than when you want distance: ``colony_block_user`` is the tool for that. Idempotent — calling it again refreshes the window rather than erroring. Expiry defaults to 90 days so a stale judgement lapses on its own; pass ``forever: true`` if you really mean permanently.
    ConnectorNo auth
  • Stop suggesting a specific account to you. Scoped to suggestions ONLY — this is not a block. You keep seeing their posts, they can still message you, and they are never told. Use it when a suggestion is simply wrong for you rather than when you want distance: ``colony_block_user`` is the tool for that. Idempotent — calling it again refreshes the window rather than erroring. Expiry defaults to 90 days so a stale judgement lapses on its own; pass ``forever: true`` if you really mean permanently.
    ConnectorNo auth
  • Request a free Recao account for your human. This does NOT create an active account: it registers a PENDING one and emails your human an activation link; nothing works and no terms are accepted until they click it (the human accepts the terms at activation, not you). The API key in the response stays inert until then. Consent stays with the human, so calling this is a request, not a decision made for them: in an interactive session their approval of this tool call is the go-ahead; if you run autonomously, surface this step to your human instead of calling it. After activation, reconnect with header `Authorization: Bearer <key>`.
    ConnectorNo auth
  • Analyze text for writing style issues: weasel words, passive voice, duplicate words, long sentences, nominalizations, hedging, filler adverbs, and research-cited AI tells. Read-only and stateless — text is analyzed in memory on the hosted server and never stored. Returns a plain-text report with each issue's line and column, the matched text, surrounding context, and the reason for AI tells; texts over 100,000 characters return an error message. This hosted server has no filesystem access — the wsc-mcp npm package adds a check_file tool for local files. It only reports issues — to auto-remove duplicate words, follow up with fix_duplicates.
    ConnectorNo auth
  • Replace the notes on a finished Load Test's Test Report — the only thing on a Load Test this surface edits. Ask the user before writing: notes belong to the user, and advising on a test never requires writing them. The text sent becomes the report's entire notes, so first read the current notes with get_load_test_report and preserve the user's content in what you send.
    Connector
    Destructive
    OAuth
  • Fetch one page of posts from a single subreddit, the community-monitoring primitive. subreddit_name is the name without the r/ prefix. sort defaults to the subreddit's own front-page order (best); use sort=new for monitoring. sort=top and controversial need a range, but the window is currently not applied upstream on this feed: top returns the subreddit's all-time top posts whatever range says (time-windowed tops are a known gap here; reddit_search's range DOES work for keyword queries). Costs 4 credits per page; a cursor page is a NEW call priced the same way. Reddit splices about one promoted ad into every feed page; these are dropped by default, so set include_promoted=true only when ads ARE the data you want (ad intelligence, who targets this community) -- kept ads carry is_promoted=true. Returns post summaries (title, author, upvotes, comment_count, created_at, permalink, id) with a cursor for older posts; bodies and discussions come from reddit_get_post with the returned ids. For keyword search across all of Reddit use reddit_search; this tool takes no query.
    ConnectorOAuth
  • Fetch one X account's profile: name, bio, location, website, follower/following counts, tweet and media counts, verification state, and join date. identifier accepts a screen name without the @ (e.g. 'nasa'), a full x.com or twitter.com profile URL, or the numeric account id; numeric strings are treated as ids, and the rare all-digit handle can be forced with by='screen_name'. Costs 4 credits. The returned platform_fields.id is stable across handle changes; store it for repeat lookups. To find accounts by topic use x_search type=people, and to read what an account posts use x_get_tweets; this tool returns no tweets.
    ConnectorOAuth
  • <summary>Query the LinkedIn posts the user tracks: their own posts (metrics refreshed daily M-F) plus third-party posts registered via fetch_post_engagers. `is_own_post` distinguishes the two — third-party rows carry the author's name/headline in author_name/author_headline. Use this to answer "which of my posts performed best?", "what's my average engagement?", "show me posts from last month", etc. This is the account-global table, with no agent/monitor dimension — for the feed a specific agent's monitors discovered (and to act on it), call query_monitored_posts. Columns: id, social_id, text, share_url, posted_at, impressions, reactions, comments, reposts, is_own_post, author_name, author_headline, fetched_at, created_at, plus a derived engagement_rate string (reactions+comments+reposts over impressions, matching the UI) — '0.0' for posts with no impression data (e.g. third-party posts). The engagement_rate is computed after the query runs, so it can't appear in where_clause or order_by; filter and sort on the raw columns instead.</summary> <returns> <description>Dict with count, truncated, and posts array (each row carries the columns above plus the derived engagement_rate).</description> </returns>
    ConnectorOAuth
  • Returns what the GunSpec API reference documents for an endpoint: its parameters and accepted values, the plan it needs, whether a key is required, caching, every error status with the error.reason values to branch on, and the languages a sample is printed in. Use this tool before writing or explaining code that calls the GunSpec API, instead of recalling parameters. The path may be a template (/v1/firearms/{id}), a concrete path or a URL; a partial path such as /v1/vendor lists the operations under it.
    ConnectorAPI key
  • Reddit posts matching a query, ranked by the search, across all of Reddit or inside one community. Use when: "what do people on Reddit say about X", "find threads complaining about Y", "who is asking for a tool like ours". Not for: everything new in a community since you last looked, use reddit_get_new_posts (ranked search is never complete). Reading one thread, use reddit_get_post and reddit_get_comments. Choosing communities to watch, use reddit_search_subreddits. Returns: List, ranked, not exhaustive. rows[]: id, subreddit, title, author, created_at, score, comments, upvote_ratio, url, link_url, body (cut at 2000 characters), flair, over_18, is_video. Cost: 1 credit per call, up to about 25 posts; nothing on NoData. Cached 1 hour. Example: {"query": "hubspot alternative", "sort": "new", "time_range": "month"}
    ConnectorAPI key
  • The posts in one Facebook group, newest first. Use when: watching a community you sell into, the way reddit_get_new_posts watches a subreddit. Not for: a page's own posts, use facebook_get_posts. A complete window since a moment, which Facebook does not offer: page with the cursor and dedupe on id. Returns: List. rows[]: posts with author and author_followers, created_at, text (cut at 2000 characters), likes, comments, shares, saves, views, media, duration_s, links, transcript and top_comments[]. top_comments are the comments Facebook shows under the post, with each commenter's profile URL. null or empty = the platform does not publish it. Give the group's url. Cost: 1 credit per page. Cached 6 hours. Example: {"url": "https://www.facebook.com/groups/742354120555345"}
    ConnectorAPI key
  • Changes a saved post in place, keeping its id: caption, media, channels, per-network settings and time. Send the whole post as for create_post — what is left out is removed. Works on drafts, posts awaiting approval and scheduled posts; a post a network has already published, one going out right now, or one handed over in parts is refused. draft: true takes a scheduled post back to a draft. Under a review-mode credential an edited post keeps waiting for approval, and a scheduled post cannot be changed. Run validate_post first. Moving a post without changing it is reschedule_post.
    Connector
    Destructive
    OAuth
  • Analyzes the content of attachments (images, videos, audio, PDFs, documents) from posts on the padlet. - Purpose: Retrieve and analyze post attachment content so you can describe, summarize, or answer questions about what's in the attachments. - What this tool returns: { success: true, analysis: { posts: [{ post_id, attachments: [{ description }] }] } } with a structured analysis grouped by post_id; { success: true, message: "No valid attachments to analyze" } when none of the posts has an attachment it can read; otherwise { success: false, message: "..." }. Guidance for use: - Use this tool when the user asks about the content of images, videos, audio, documents, or other attachments in posts. - Identify which posts have attachments before calling. If an EXPLICIT list of post_ids to analyze has been provided to you in the conversation, use those directly. Otherwise, call `get_padlet_content` first to discover them. - A post has an attachment if its "attachment" field contains a URL (not empty, not "poll"). Check BOTH the "attachment" field and "attachment_props" — some posts have a URL in "attachment" but empty "attachment_props". - Pass the post_ids of posts whose attachments you want to analyze. The tool will retrieve the attachment URLs automatically. - Pass at most 50 post IDs per call. If there are more, prioritize the most relevant posts. - Only analyzes attachments the current user has permission to view. - Do not use this tool if the user is not asking about attachment content. - Results are cached: previously analyzed attachments return cached descriptions without re-analyzing. - IMPORTANT: Only pass the `query` parameter when the user has a specific, targeted question about the attachment content (e.g. "What formula is on slide 3?", "What color is the logo?"). For general requests like "describe the attachments", "what's in the images", or "summarize the content", do NOT pass a `query` — omit it entirely so the tool returns a comprehensive generic description.
    ConnectorOAuth