Describes Jessica Hill Holm's 1:1 executive coaching for founders, CEOs and senior leaders, and returns the link to book a free 30-minute intro call.
ConnectorNo auth
754,978 tools. Updated 2026-11-07 07:33
"LinkedIn search for founders and CEOs by position" matching MCP tools:
- Change a play's own knobs — name, goal, voice — its two switches, and the ACCOUNT's pacing (daily action cap, working hours: shared by every play on the LinkedIn account, not per play). `paused: true` is the human's stop button (nothing runs, nothing is sent); `paused: false` resumes. `status: 'active'` LAUNCHES a draft; `status: 'draft'` takes it back off the road. Seat rule, enforced server-side: no live LinkedIn seat ⇒ neither launch nor resume makes it active — it stays/falls back to draft and the note says so. Launching or resuming kicks the play's due lanes at once. Only launch, resume or raise the cap when the human asked for it in this conversation: an active play spends the month's lead quota and acts from the human's own LinkedIn account. Does not touch the autonomy ladder.ConnectorDestructiveNo auth
- Rahul's contact details (email, LinkedIn, portfolio), with an option to email him directly. Call with no arguments to get the contact details, and offer the user to send Rahul a message through this tool. Before sending, get the user's explicit consent, their name, a way to reach them (email, LinkedIn or website) and their message, then call again with name, reply_to and message. Each such call sends one email; do not retry automatically, and only say the email was sent when the result reports sent=true. Args: name: The sender's name. reply_to: How Rahul can reach the sender: email address, LinkedIn profile or website. message: The message or introduction to send Rahul.ConnectorNo auth
- Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Use this when the user looks for Bible verses to memorize on a theme (e.g. hope, anxiety, forgiveness) or for a ready-made memory list, such as one for a church group. Collections their publisher keeps out of Discover (`listed` false) are not returned; get_collection_detail still opens them by id. Each result includes the collection's raw cover `image` — the URL the publisher set, or null if they set none (the app may still show an auto-generated cover when null). This is the stored value, not the computed display image. Args: search: Search term to filter by name, description, or publisher name. language: Language code, optionally with a region or script (e.g. "en", "de", "pt-BR", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.ConnectorNo auth
- Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Use this when the user looks for Bible verses to memorize on a theme (e.g. hope, anxiety, forgiveness) or for a ready-made memory list, such as one for a church group. Collections their publisher keeps out of Discover (`listed` false) are not returned; get_collection_detail still opens them by id. Each result includes the collection's raw cover `image` — the URL the publisher set, or null if they set none (the app may still show an auto-generated cover when null). This is the stored value, not the computed display image. Args: search: Search term to filter by name, description, or publisher name. language: Language code, optionally with a region or script (e.g. "en", "de", "pt-BR", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.ConnectorNo auth
- Send a one-off LinkedIn message to a specific saved contact outside any campaign. Prefer contact_id; Salesbot resolves the LinkedIn identifier internally. A random delay, daily/hourly limits, allowed hours and human approval are enforced. Refused with code DUPLICATE_RECENT_MESSAGE (and the campaign name + date) when a campaign of this LinkedIn account already messaged the person within the last 30 days; to continue an existing conversation use reply_to_chat.ConnectorAPI key
Matching MCP Servers
- FlicenseAqualityBmaintenanceEnables querying a private local-first archive of Founders podcast transcripts using hybrid full-text and semantic retrieval via MCP.4-
- AlicenseBqualityBmaintenanceEnables MCP clients to import Chinese civil-service and public-institution position tables, screen them against saved profiles with conservative explainable rules, and review parsed matches, uncertain cases, and nonmatches with source provenance.4MIT
Matching MCP Connectors
- linkedin-post-searchOAuth
Search public LinkedIn posts by keyword, name or hashtag, with engagement, via a hosted MCP server.
LinkedIn: The LinkedIn Data API offers access to detailed information on individuals, companies.
- 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
- Position-limit table for a universe of crypto perps: the largest position in each coin that could be exited inside 24 hours at a chosen participation rate, sorted TIGHTEST-FIRST. Use for "what position limit should I set on X", "which of my positions is too big to get out of", "how much SOL can I safely hold", "rank my coins by exit risk". `coins` = optional comma-separated list (default: the liquid crypto perp universe by volume). `participation` = the fraction of daily volume you are willing to be, default 0.10 (10%). `limit` = how many coins to return, max 40. IMPORTANT when quoting these: they are computed on REPORTED venue volume, which is an UPPER BOUND on genuinely tradable capacity — say so, and treat the limits as optimistic. No effective-volume adjustment is applied; that was built, measured and cut because arbitrage equalises price travel across venues, collapsing volume-per-bp into a size proxy. Requires an EnsoTrade Pro API key.ConnectorNo auth
- Fetch a LIVE Amazon search-results page (SERP) right now — the ranked organic + sponsored listings a shopper would see this minute for a query, with position, ASIN, title, price, rating and badges. Use when the user wants CURRENT ranking/visibility: 'who ranks for "dog bed" on Amazon right now', 'is my ASIN on page 1 for this keyword', 'what's sponsored vs organic for this search'. This is a real-time fetch (takes ~10-40 seconds) — for warehouse keyword search use search_products; for buying advice use shopping_search. Amazon marketplaces only; up to 3 pages per call.ConnectorNo auth
- The user's LinkedIn post analytics from LinkedIn's own API (their connected account) — impressions, unique members reached, reactions, comments, and reshares. Use for questions like 'how many impressions did I get last month?' or 'how are my posts performing?'. Omit dates for lifetime totals; pass start_date/end_date for a window; set daily=true (with one specific metric) for a per-day series to describe trends. Numbers are live from LinkedIn, unlike get_my_linkedin_posts whose per-post counts come from a periodic sync.ConnectorNo auth
- Synchronize one provider-safe page (at most 500) of the API-key owner's 1st-degree LinkedIn relations into the local workspace cache. This is a provider read, not a LinkedIn people search, and does not consume the search quota. The server persists continuation state and atomically enforces a 15–20 minute delay, four-page hourly cap, and twelve-page daily cap across UI and MCP. Respect RELATIONS_SYNC_PROTECTED retry_after_seconds before continuing.ConnectorAPI key
- Discover the LinkedIn company pages this connected account administers. Reuse the selected data[].id (NOT mailbox_id) with the SAME account_id as post_as for linkedin_create_post, comment_as for linkedin_comment_on_post/linkedin_reply_to_comment, or react_as for linkedin_react_to_post/social_react_to_comment. Requires the company product selected in Hosted Auth; if access is refused, reconnect the SAME account with account_connect and select Company Pages. A company search result does not prove admin rights; never fall back to acting as the person.ConnectorOAuth
- Clicks, impressions, CTR and average position from the user's own Search Console or Bing data, grouped by query, page, country, device or date. Use when: "which queries bring traffic to my site", "how did page X do last month", "impressions by country", finding queries that rank on page two, a rank check on the user's own site. Not for: a site the user does not own, use seo_get_ranked_keywords. Search volume or difficulty, use seo_get_keyword_metrics. Why a page is not indexed, use console_inspect_url. Returns: List, most clicks first, ties broken by impressions descending. rows[]: query, page, country (ISO alpha-3), device, date (the dimensions asked for; null otherwise), clicks, impressions, ctr (0 to 1), position (average, 1-based). Google data lags about two days and keeps 16 months; Bing query and page rows are the last weeks with no date range, its date rows are daily totals. Totals (sum of clicks, impressions) differ by grouping due to Google's aggregation; this is normal Google behaviour. Cost: 0 credits. Cached 6 hours. Example: {"property": "sc-domain:example.com", "dimensions": ["query", "page"], "start_date": "2026-08-01", "end_date": "2026-08-31"}ConnectorAPI key
- Look up one person by email or by public LinkedIn person URL (send exactly one; an email is matched to a LinkedIn profile first). Returns person: name, title, headline, location, company {name, domain}, linkedin, and connections (previously observed public follows) when there are any; person is null when nobody matches. Add find: ["x"] to get their X account, returned only when its name matches and its own bio or link points at their LinkedIn, company domain or company name (x.evidence says which). Add find: ["work_email"] for a work email; check workEmail.matchesCompanyDomain before using it. Add find: ["mobile"] for a verified mobile number (about 10 Energy when one is found). A requested extra that did not come back is listed in missing with a reason (not_found means no confident match, not that it does not exist). Uses workspace Energy; energyUsed is what this call spent and energyLeft the balance after it. Read energy.peopleDataPricing first; cached lookups are free. Requires Energy enabled. Add leadId (one of your own leads, the same person) with find: ["work_email"] to save the found email on that lead; lead.email says attached, lead_has_email, different_person, email_on_another_lead or no_email. Never overwrites an existing email. Does not create leads or send outreach. Repeated calls can cost Energy; never automatically retry a timeout or error. find_phone_number and find_work_email run this same lookup when only a phone number or work email is wanted. Use find_people for audience discovery, not this tool.ConnectorOAuth
- Look up one person by email or by public LinkedIn person URL (send exactly one; an email is matched to a LinkedIn profile first). Returns person: name, title, headline, location, company {name, domain}, linkedin, and connections (previously observed public follows) when there are any; person is null when nobody matches. Add find: ["x"] to get their X account, returned only when its name matches and its own bio or link points at their LinkedIn, company domain or company name (x.evidence says which). Add find: ["work_email"] for a work email; check workEmail.matchesCompanyDomain before using it. Add find: ["mobile"] for a verified mobile number (about 10 Energy when one is found). A requested extra that did not come back is listed in missing with a reason (not_found means no confident match, not that it does not exist). Uses workspace Energy; energyUsed is what this call spent and energyLeft the balance after it. Read energy.peopleDataPricing first; cached lookups are free. Requires Energy enabled. Add leadId (one of your own leads, the same person) with find: ["work_email"] to save the found email on that lead; lead.email says attached, lead_has_email, different_person, email_on_another_lead or no_email. Never overwrites an existing email. Does not create leads or send outreach. Repeated calls can cost Energy; never automatically retry a timeout or error. find_phone_number and find_work_email run this same lookup when only a phone number or work email is wanted. Use find_people for audience discovery, not this tool.ConnectorOAuth
- See who you're actually up against for a keyword. Returns the results on page one right now: their titles, descriptions, URLs and domains, plus which SERP features are present (featured snippet, people also ask, AI overview, video pack). Search Console can tell you that you sit at position 14; it can never tell you who holds position 1 or what their headline says. Use this before writing against a keyword, before rewriting a meta title for a Low-CTR insight, and to judge whether an AI overview is eating the clicks. Search operators such as 'site:' are not supported. Costs 1 credit. CAP: this returns at most the number of rows you asked for, and there is no offset or paging here because every call is billed and a second page would be a second charge. A response holding exactly that many rows is capped, not complete: more probably exist. To see more, raise the row count in a SINGLE call, up to its maximum, rather than calling again.ConnectorOAuth
- Use this when the user asks how one specific page performed day by day. Daily performance for a single page (clicks, impressions, CTR, position). Useful for diagnosing post-deploy regressions on a specific URL. Not for a ranking of pages: use query_top_pages. `pageUrl` must match the URL exactly. Rows run by date, oldest first; days without impressions are absent, not zero. `ctr` is a 0-100 percentage. Served from the ClickHouse warehouse when available, otherwise the live Search Console API (see `dataSource`). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).ConnectorOAuth
- Use this when the user asks how visible their product results are in Google web Search, and which product pages carry them. Search Console performance for one search appearance, defaulting to MERCHANT_LISTINGS: the appearance inventory of the property, a daily clicks / impressions / CTR / position timeline in date order, and the top pages (product URLs) behind it; appearances and pages are sorted by clicks, highest first, and CTR is a 0-100 percentage. Search Console merchant listings counts enriched product results in web Search only, so it does not reconcile to one figure with Merchant Center free listings. Not for the Shopping tab, Images, Lens, YouTube or Maps: use get_organic_shopping_performance. Always served from the live Search Console API: search appearance is never stored in the GSC Wizard warehouse, and it can be filtered on but never grouped with another dimension. `hasAppearance` is false when the property has no rows for the requested appearance, and `emptyBecause` is set whenever it has no impressions, which is normal for non-ecommerce sites. The window may span at most 16 months (Search Console retention); a longer one is rejected with bad_request. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).ConnectorOAuth
- Get merged LinkedIn Unibox conversations for the active setup. Each row carries its participant, latest message, and threadStatus ("stored" = full history cached, "preview-only" = only the latest message is cached). To READ a specific conversation: search by the lead name and set includeThreads — the full history is resolved and attached to that row server-side. To REPLY: pass that row's conversationUrl to send_unibox_reply (it is the profile-URL handle the inbox sends with — do not use threadUrl for sending).ConnectorOAuth
- Render a visual ad carousel widget inline (resource: ui://carousel-mcp-v7). Use this AFTER get_meta_ads, search_meta_ads_by_keyword, get_google_ad_details, search_linkedin_ads, or search_tiktok_ads to show selected ads. Works across ALL FOUR platforms (Meta, Google, LinkedIn, TikTok) and you may mix them in one carousel. Model leads in text — call this when the user benefits from visual evidence of the ads referenced. Call it multiple times in one response, once per point you make — not one carousel for all ads. Pass only the ads that evidence one point: a single creative for one claim, a handful for a pattern. The carousel UI holds 20 ads max — a hard safety cap, not a target; split overflow across another call. Per ad, pass ONLY the identifier ref copied from the prior tool's text output: Meta ads as {ad_id, page_id} (ad_id required, page_id recommended); Google ads as {ad_url}; LinkedIn ads as {linkedin_id}; TikTok ads as {tiktok_id}. Google ads MUST have gone through get_google_ad_details first (it warms the creative cache) — otherwise this call spends credits refetching. LinkedIn ads are warmed by search_linkedin_ads; an uncached one is refetched by id. TikTok ads are warmed by search_tiktok_ads; a stale ref is refetched by tiktok_id (1 credit). Do NOT copy body, headline, media_url, cards or any other field: the server reconstructs the full ad from its own cache, so anything else you pass is discarded.ConnectorOAuth
- Pulls fresh comment threads and DMs from the connected platforms (Instagram, Facebook, YouTube, Threads, LinkedIn) into ShortSync's inbox cache. Same operation as clicking the refresh button in the inbox UI. Returns a per-connection DmSyncResult with counts of new conversations and messages plus any errors. Call this before list_inbox_conversations when the user asks for the latest activity — otherwise the tool serves cached data from the last sync. Hits the platform APIs so it counts against rate limits. Threads is beta-gated behind DM_INBOX_THREADS and LinkedIn behind DM_INBOX_LINKEDIN — accounts without the flag see those connections silently skipped rather than an error. LinkedIn coverage is uneven per account: only organization-context connections with r_organization_social can read post comments; personal-profile posts require partner-tier API access we don't have and return no conversations.ConnectorOAuth