Skip to main content
Glama
795,924 tools. Updated 2026-11-17 12:47

"A professional networking platform" matching MCP tools:

  • Create a new ad group under a campaign. Every ad group belongs to one platform (body.platform, a platform id such as google-ads): only that platform receives it, its ads and its keywords. Leave it out on a campaign that runs on one platform; name it on a campaign that runs on several (400 AD_GROUP_PLATFORM_REQUIRED lists them). It is fixed once created — use copy_ad_group to run the same ads elsewhere. Returns the full updated/created object. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.
    ConnectorAPI key
  • Get Alex Polonsky's curated public professional profile, including selected experience, demonstrated capabilities, journalism background, public projects, and future professional directions. This is selected evidence, not a complete CV. When summarizing examples, preserve their ownership qualifier exactly: led, owned_key_aspects, or contributed. Do not infer stronger ownership. If a list mixes things Alex built with work he contributed to or helped bring to market, frame it as built or contributed to, not built. Keep the action verbs and limits from contribution; do not reduce a contribution to an artifact name. Separate demonstrated experience from future directions. Use get_availability for current opportunity status.
    ConnectorNo auth
  • Given a LinkedIn profile URL, return that person's professional email address, verified live, with their current role and company. Use this when you have someone's LinkedIn page and need to email them; for a name and company without a URL use find_work_email. Spends 3 credits, refunded if no email is found.
    ConnectorNo auth
  • Use this when the user wants the numbers for their posts: "how are my clips doing", "which TikTok took off", "how many views did my Short get", "show my scheduled posts". Returns per post the platform, status, post URL, caption, clip title, the latest views, likes, comments, shares and saves the platform sent (null = the platform sends no such count) and views at 1 hour, 24 hours and 7 days. platform: tiktok, youtube, instagram, ... or all (default). status filters draft, scheduled, posted or failed (empty = all; status "draft" lists the post_id that update_draft and delete_draft take). limit 1-50, newest first. Covers posts RipClip published or planned. Not for: a recap of the week (weekly_report), platform against platform (compare_platforms), what is growing fast (whats_taking_off) or follower counts (get_account_stats). Free and read only.
    ConnectorNo auth
  • The editor's highlight menu: rewrite, condense, expand, simplify, proofread, make more professional or casual, or follow an instruction ('ask'), for ONE passage of a draft. Returns the proposed text and saves nothing; show it to the person, then apply it with verand_edit_article (find = the original passage). Costs a small model call. Check the proposal before showing it: if it adds a figure or claim the original didn't have, take it out or bracket it.
    ConnectorOAuth
  • Add recipients to the API Platform (Email API / SMTP) suppression list so they are rejected on future API Platform sends. It does NOT stop Marketing Platform campaigns: to stop campaigns reaching an address, unsubscribe the contact (update_contact) or import it as suppressed in the panel. Scopes: global (default) blocks every API Platform send; marketing blocks only PROMOTIONAL Email API messages (metadata campaignType PROMOTIONAL), NOT Marketing Platform campaigns; transactional blocks only transactional (non-promotional) API Platform messages. The request is all-or-nothing: an invalid address rejects the whole batch. This blocks future mail to those addresses — confirm with the user first. Set dry_run: true to validate without changing anything.
    Connector
    Destructive
    API key

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Local-first MCP server for research on AI-assisted browsing of a user-owned professional-network account (e.g., LinkedIn), providing read-focused tools such as profile, company, search, and feed reads.
    MIT

Matching MCP Connectors

  • Delete a post from iHatePosting. ONE SEND AT A TIME: a SCHEDULED post going to several accounts is stored as one post PER SEND, so deleting one cancels only that platform and leaves the rest scheduled — pass the `postId` that create_post returned on that particular send, or the id of the row list_posts shows for it. There is no need to cancel a whole multi-platform post to drop one platform from it. A DRAFT IS DIFFERENT: until it is scheduled, a draft is ONE post holding every platform it is aimed at (all its sends share one postId), so deleting it removes every platform — to drop one platform from a draft, use update_post with the remaining accountIds instead. The reply's `platformsRemoved` names every platform the delete took; for one send of a group, `stillScheduled` lists the sends still going out and `otherSends` the rest of the group (already published or failed), each with its status; their `scheduledAt` is UTC (it ends in Z) and `scheduledLocal` is the same moment in the account owner's timezone — report that one. THIS DOES NOT UNPUBLISH ANYTHING: a post that has already gone out stays live on the network, and deleting it here only removes iHatePosting's record of it. For that reason a published post is refused unless you pass force: true, and you should only do that after telling the user in words that the platform post will remain. A post that is publishing at this moment is never deletable, forced or not — the worker is mid-flight on it. Deleting a scheduled post stops it going out.
    Connector
    Destructive
    No auth
  • Metrics for this workspace's published posts. Returns a summary totalled across every published post (post count, overall totals, totals per platform), plus the newest posts in detail, each with one entry per platform it went to: impressions, reach, views, likes, comments, shares and saves. A metric is null when that platform does not report it; supported=false means nothing can be read for that target (no analytics for the platform, or no post id yet). Values are the last stored reading, not a live fetch, and fetchedAt says when it was taken. Use this to answer whether posts worked. It covers published posts only: use list_posts for drafts and scheduled posts, get_post for one post's details, and get_link_in_bio for visits to the link-in-bio page.
    ConnectorAPI key
  • One Instagram account: followers, posts and whether it is a business account. Use when: sizing a creator or a brand, checking a handle, reading a bio and its link before outreach. Not for: the account's posts, use instagram_get_posts or instagram_get_reels. Posts by topic, use instagram_search_posts. Returns: Record. The account's handle, name, bio, verified, followers, following, website, links (its other bio links), email and phone (a business account's public contact buttons) and related (accounts Instagram suggests beside it), with other profile fields where Instagram fills them. null or empty = the platform does not publish it. posts_count is null: a signed-out visitor is shown 12 posts whatever the account has, so count posts from instagram_get_posts. kind is company only when Instagram flags a business account; many brands use a creator-style professional account and read person, so judge a brand by industry and bio. Cost: 1 credit. Cached 24 hours. Example: {"handle": "gymshark"}
    ConnectorAPI key
  • Get the household insurance record: life policies with sourced death benefit, face amount, cash value, coverage by type, and staleness, plus auto, homeowners, and umbrella policies with the limits, deductibles, named insured, property address, policy dates, premium, and currency X1 read from uploaded declarations. This tool never determines coverage adequacy. Do not answer that coverage is adequate, inadequate, sufficient, insufficient, overinsured, or underinsured; use coverageReviewPolicy.requiredStatement and route the judgment to a licensed professional. The response names the resolved household and must never be attributed to another person. A professional sees only facts read from documents shared with them; exclusions and endorsements are not extracted. Professionals must pass clientId for a client unless X1 already supplied a client-scoped context; a professional who also has their own household in X1 omits it to read their own. Scoped specialists are excluded unless a future explicit permission adds insurance-context access.
    ConnectorAPI key
  • Save a task draft on Muovi for the person you are helping, and get back a link for them. The person opens the link, reviews the draft, signs in to Muovi and publishes it themselves. This tool publishes nothing and does not notify any professional. To hand over the full request, call `muovi_get_service_requirements` for the service first and collect the required fields it lists, asking one question per message and waiting for the answer before asking the next. A draft whose `urgency` is `flexible` is complete without the date. Also ask what a professional would need to quote this specific job, skip anything the person already said, and write those details into `description`; no list of job questions is prescribed. Send the answers in `slots` (keyed by slot key) with `location`. Do not ask the optional slots as a list; when what the person has told you, at any point in the conversation, gives an optional slot's value, send it in `slots` as well as writing it in `description`. If a required answer is missing, the result has `status: "incomplete"`, lists the questions still to ask and carries no link: ask them one per message and call again with every answer. If a value is not accepted, the result has `status: "invalid_slots"` and names each slot. A draft with every required answer opens on a review form with those answers filled in, without asking them again, unless Muovi's assistant has a question of its own for the person, and the person confirms the address on Muovi's map after opening the link, before publishing. Sending only `description` still saves a draft, and that link opens Muovi's assistant, which asks the person its questions. To direct the draft to one professional, pass `professional_id`, the `id` of any result from `muovi_search_professionals`: when the person publishes it, the task goes to that professional first for 24 hours and then opens to everyone, unless `open_to_others` is true, in which case it opens to everyone right away and that professional is still told. Set `open_to_others` from what the person chose; they can change it on the review form. A ProSite slug in `professional_slug` is still accepted instead of `professional_id`. Leave both out for a general request to get offers from several professionals. `service_slug` comes from `muovi_list_services`. A link nobody has opened expires 24 hours after it is created. The first person to open it takes the draft, signed in or not, and can reopen the link for up to 7 days, so give it only to that person. Do not include phone numbers, email addresses or other contact details in any text.
    ConnectorNo auth
  • Search every upcoming Bay Area event by words, dates, price, topic or place: dance, AI, music, arts, food, sports, comedy, exercise, volunteering, dating, business and professional networking. Use it whenever the question has search words, a date range ("this weekend": from/to), free-only, a town or an area; for a day-by-day overview of the next few days with no search words use list_upcoming, for one act by name find_performer. Words in `query` match the title, venue, performers, organizer or tags at the start of a word, singular or plural, with common synonyms (standup = stand-up, kids = children); by default all of them must match, with match "any" (or | / commas between them) any one does. A word that matches nothing is read as the closest word the events use, and `search` in the result says how the query was read. Dates are local (America/Los_Angeles), YYYY-MM-DD. Keyword results come earliest first, at most `limit`; `count` says how many matched in total. Topic/audience tags and venue mapping are incomplete: retry without optional filters when thin, use semantic search when offered, and supplement with web search if there are too few verified options. Check original listings for indoor setting, exact age eligibility, price and remaining tickets. Zero results do not mean no events exist. get_city lists valid filter values. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
    ConnectorNo auth
  • Find the data sources an account can put on a dashboard, across every platform it has connected. Use when: the user wants a source on a dashboard and you have no sourceId for it — search first, then pass what comes back to add_data_source_to_dashboard. Searches two things. Sources DashThis already holds are found straight away, whatever the platform. Sources that exist on the platform but nobody has picked yet are found only once the search names ONE connection — asking every connection would mean calling every platform — so pass 'connection' (or an 'integration' the account has only one connection to) when the first search comes up short. Returns: each source with its connectionId and providerKey, plus a sourceId when it is already set up; and the connections searched, so you can narrow to one. Rules: this creates nothing and changes nothing. If several sources could be meant, put them to the user and let them choose — never guess, because the wrong one puts another client's numbers on a report. Then: name the source, its platform and its connection when you report back — one client often has several accounts on the same platform — and its status when it is in error.
    ConnectorOAuth
  • Delete a published post from its platforms, by its `post_id` — every platform it is live on, or only `platform`. There is no need to call get_delivery_receipt first. There is no undo; reposting is a new post with a new URL. This is the person's own decision about their live post, not a cleanup step. Each delivery answers in `deliveries`: `error_code` `never_went_out`, `account_gone` or `unsupported` means the person removes it on the platform themselves; only `platform_refused` is `retriable`. `delivery_id` still takes down one delivery; a post id passed there answers `is_post_id` with the post's `deliveries`.
    Connector
    Destructive
    API key
  • Change an existing draft or scheduled post: its publish time (post_at), its caption, per-platform captions, or its status (draft or scheduled). Fields you omit are left as they are. Call get_scheduled_post first to see the post's targets and captions. For a post with one platform, pass caption. For a post sent to several platforms, pass captions with one entry per platform to change; platforms you leave out keep their caption. If a post has two targets on the same platform, identify each by target_id (listed by get_scheduled_post) instead of provider. Setting status to "scheduled" queues the post to publish at post_at to the connected social accounts. Published or in-progress posts cannot be edited and are rejected.
    Connector
    Destructive
    OAuth
  • Discover where a list can go in an Ad Platform Export: the ad platforms REACH supports, whether the user has connected each one, and the ad accounts of connected platforms. Pass `platform` and `account_id` to also get that account's existing Ad Platform Audiences, which `export_list_to_ads` can add to with `audience_id`. Pass `list_id` to see whether that list can be exported to each platform, and why not: only a list with Online Audience output can be, each platform has a minimum record count, and an expired list (`list_expired`, past its `expires_at`) can't be exported at all, so the user needs a new list, for example by running the job again. An unconnected platform is listed with `connected: false`. Connecting happens only in the REACH web app, on the Integrations page; ask the user to do it there.
    ConnectorOAuth
  • Start an Ad Platform Export: push a list's Online Audience to the user's connected ad account as an Ad Platform Audience. Not billed. Find the platform, `account_id` and, to add to an existing Ad Platform Audience, its `audience_id` with `ads_export_options`. Pass `audience_name` to create a new Ad Platform Audience instead. The export runs in the background; check it with `ads_export_status` and the returned `history_id`. Only one export of a list to a platform runs at a time. When one is already running, no new export starts: `already_in_progress` is true and the response describes the running export, whose account and audience may differ from this request.
    Connector
    Destructive
    OAuth
  • Cancel the account's card-paid Professional plan at period end (provider "stripe", undo to keep it), or its PayPal subscription (provider "paypal"), exactly as the account page does. Prepaid terms bought with the balance never renew, so need no cancelling. Needs the "billing" scope.
    Connector
    Destructive
    No auth
  • Search for a term (a brand, product, domain or competitor) across up to 10 social platforms once, keeping only posts that mention it. Costs 1 credit per platform that answers, even if nothing on it mentions the term; a failed or empty platform costs nothing. Stores nothing and schedules nothing: use create_monitor to keep watching. Reports what happened on each platform, so read sources before concluding there are no mentions.
    ConnectorNo auth
  • Add recipients to the API Platform (Email API / SMTP) suppression list so they are rejected on future API Platform sends. It does NOT stop Marketing Platform campaigns: to stop campaigns reaching an address, unsubscribe the contact (update_contact) or import it as suppressed in the panel. Scopes: global (default) blocks every API Platform send; marketing blocks only PROMOTIONAL Email API messages (metadata campaignType PROMOTIONAL), NOT Marketing Platform campaigns; transactional blocks only transactional (non-promotional) API Platform messages. The request is all-or-nothing: an invalid address rejects the whole batch. This blocks future mail to those addresses — confirm with the user first. Set dry_run: true to validate without changing anything.
    Connector
    Destructive
    API key
  • The platform's own overview for one connected account, by `platform`. linkedin: a personal LinkedIn profile's aggregated post analytics (impressions, members reached, reactions, comments, reshares, followers) over an optional dateRange; a LinkedIn Page (organization account) is refused here, get_account_analytics and list_linkedin_live_posts cover a Page. youtube: channel statistics (subscribers, total views, video count) and the latest uploads with per-video stats; limit up to 50, default 15. bluesky: profile stats (followers, following, post count) and recent posts with per-post metrics; limit up to 50, default 20. pinterest: a 30-day account summary and recent pins with per-pin metrics. instagram, facebook, threads: the Meta-family overview; availability varies per account, so the response may be real metrics, {state: "permissions_required"} (platform permissions pending) or {state: "unavailable"} (the platform refused the fetch), and those states carry no numbers. dateRange (LinkedIn) and limit (YouTube, Bluesky) are refused on any other platform. An expired connection returns a reconnect error. For one account over any date range with a per-post table, on every platform, use get_account_analytics.
    ConnectorOAuth