"A search for advanced LinkedIn features or tools for exploring profiles and connections" matching MCP tools:

• search_google_xrayA

  LinkedIn MCP Server (Salesbot)A

  Google X-Ray search for public LinkedIn profiles via Google operators (site:linkedin.com/in). Useful when you don't want to consume LinkedIn search limits, and it CAN target a specific person (put the name/company in `keywords`). Found profiles are saved into your contacts (in a 'Google X-Ray' list, deduplicated by profile URL). Returns JSON `{ found, saved, rejected_low_quality, contacts, … }` where each item in `contacts` has `contact_id`, `full_name`, `profile_url` (note: this tool returns `contacts`/`profile_url`, unlike search_linkedin_people which returns `results`/`linkedin_url`). Saved leads are UNVERIFIED cached snippets — run enrich_contacts before trusting the current company. To move them into the CRM, add them to a campaign with add_contacts_to_campaign (auto-creates CRM leads) or use a CRM tool like set_deal_stage.

  ConnectorNo auth

• random_usersA

  Synthetic Data — Random UserA

  Generate synthetic / fake user profiles via the MwVideos random_users API (POST /mwvideos/api/random_users). Returns name, gender, location, email, login, dob, phone, picture, and nat. Use when the user asks for random users, fake people, sample contacts, demo personas, UI fixtures, or test profiles. Pass `results` for how many profiles (default 1, minimum 1) and `isPro` as 0 or 1 when relevant (default 0). Authenticated user_id is injected server-side — do not invent profiles; always call this tool. These are FAKE people for demos and testing, not real PII.

  ConnectorOAuth

• exploreA

  ThinAir GeoA

  BROWSING / DISCOVERY search — administrative places (cities, neighbourhoods, boroughs, counties, regions) near a location. Use this when the user is exploring a REGION rather than looking for a specific category. Supports population filtering ('cities > 100k'), ranking by significance or distance, and layer filtering (locality / neighbourhood / borough / county / region). Venues, addresses and streets are NOT served here — for venues and POI categories (gas, food, charging, etc.) use `search_places` instead. Each result carries its distance in the caller's units and a bearing from the center.

  ConnectorOAuth

• list_platformsA

  BulkPublishA

  List every social platform BulkPublish supports and whether it is currently available. Check this before telling a user they can connect a platform or scheduling a post to one: a platform in state 'off' rejects post creation with a 403 PLATFORM_DISABLED error and holds any already-scheduled posts until it is re-enabled, and one in state 'connect_off' cannot accept new connections although existing channels keep publishing. Disabled platforms are still listed, with enabled=false and a reason. A platform may also carry a 'variants' object keyed by channel accountType for sub-platforms gated on their own: LinkedIn reports variants.organization for company pages (a separate LinkedIn app with its own review), while the platform-level state covers personal profiles — so pages can be paused while personal-profile posting is live. A variant is never more permissive than its parent, and when a variant blocks a write the 403 PLATFORM_DISABLED error carries an accountType field naming it. Use this when the user asks which platforms are supported or available, or a connect/publish attempt failed with PLATFORM_DISABLED.

  ConnectorOAuth

• campaignstack_list_inbox_conversationsA

  campaignstackA

  List inbox conversations across all LinkedIn accounts in the workspace. Returns up to 50 conversations sorted by most recent activity, with participant details, last message preview, read/unread status, and associated lead info. Each conversation includes a conversationRef { platform, id } used as the identifier for other inbox tools. Use unreadOnly: true to filter to unread threads only. Use identityFilter to restrict to specific LinkedIn account IDs (use campaignstack_list_accounts to find them). Use search to find threads by a person's name or by words in the message text (2 to 200 characters); matches come back newest first with a match snippet when a message matched, and unreadOnly is ignored. Use campaignstack_get_conversation to fetch full message history for a thread.

  ConnectorAPI key

• campaignstack_send_connection_requestA

  campaignstackA

  Send a connection request to a profile. platform is required ("linkedin" - connection requests are a LinkedIn-only concept; on other networks use campaignstack_follow_profile). Target can be specified as a profileUrl (LinkedIn profile URL) or a leadId (resolved server-side to the lead's LinkedIn URL). Optionally include a personalized note (max 300 chars, LinkedIn limit). If only one LinkedIn account is connected to the workspace it is used automatically; if multiple exist, specify accountId (use campaignstack_list_accounts to find it). Subject to daily connection_request budget, weekly cap, and business hours gates unless bypassed. When true, bypasses ALL LinkedIn safety limits (daily budget, weekly caps, business hours, account status checks). ⚠️ WARNING: This disables all protections that prevent LinkedIn account restrictions. Use only when you understand the risks and accept that the account may be flagged or restricted by LinkedIn.

  Connector

  Destructive

  API key

• find_peopleA

  PeopleSearch.imA

  The list-building tool. Re-runs a plain-English people search and unlocks up to `count` full profiles in ONE atomic charge: 1 credit per newly unlocked person, and anyone you already own is free. Returns each person's real name, title, company, location, LinkedIn URL and an `id`. Emails are NOT fetched here (that is a separate credit): after unlocking, call fetch_email with each person's `id` to get their verified work email. WARNING for autonomous use: this can spend up to `count` credits in a single call, so choose `count` deliberately and confirm with the user before large batches. Returns an out-of-credits error instead of overspending.

  ConnectorNo auth

• index_videoA

  RekaA

  Index a video for search, QA, or full analysis. Processes the video through a pipeline of AI features. Typically takes 3-7 minutes; longer for long videos or the 'full' pipeline. Times out after 10 minutes by default. Pipelines: - search_only: transcription + captions + embeddings (enables search_videos) - qa_only: transcription + captions (enables ask_video) - full: transcription + captions + embeddings (enables all tools) Scene detection is enabled by default and produces scene boundaries for get_scenes. Pass scene_detection=False to skip it. Prerequisites: if using video_id, the video must be in 'uploaded' status. Use get_video to check status before calling this tool.

  ConnectorNo auth

• search-music-docsA

  Music StudioA

  Search detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.

  ConnectorNo auth

• register_derived_assetA

  VarynForgeA

  Register a derived asset (LinkedIn carousel PDF, social post, video, image) produced from an article suggestion. Appends a distribution-ledger row so the suggestion shows everything it produced — the article plus its derivatives — for content-ROI reporting (get_article_suggestion returns them as derivedAssets). Pass `channel` (reels | youtube | x | linkedin) so the app can show per-channel distribution status; register again with a new URL for repeat posts on the same channel — every registration is kept. `scheduledFor` records a future post date from an external scheduler (Buffer etc.) for display only — VarynForge never posts on your behalf. Derivative rows never affect publish status or Search Console attribution; use mark_article_published for the article itself.

  ConnectorNo auth

• c2b_appendA

  Versium REACHA

  Get business demographic details for consumers. Identify the consumer with a LinkedIn URL, or with first name, last name, and one of: email, phone, or city and state. Retrieve job title, seniority, department, business email, LinkedIn profile, and complete business information. Use this tool when users ask for 'C2B', 'c2b', or 'Consumer to Business Person' data **Tips for Best Results:** - Provide full name and consumer email for best match quality - LinkedIn URLs must be in format: linkedin.com/in/username - Use `rcfg_require_email` to return only records with business email - Use `rcfg_require_value` to filter by job title, department, or other attributes

  ConnectorOAuth

• zeekeo_create_campaignA

  rankparse-mcpA

  Creates a Zeekeo LinkedIn campaign: sends a connection invite using invite_template_id, and optionally — if followup_template_id is given — waits for the invite to be accepted, then sends a follow-up message using that template. Create templates first with zeekeo_create_template. Provide exactly one of filter_url (a LinkedIn search results URL) or profile_urls (specific profiles) as the target. This starts REAL LinkedIn automation once the campaign has profiles in it — confirm with the user before calling. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  ConnectorNo auth

• get_connection_detailsA

  YouSpotA

  Get the full profile for one of the user's LinkedIn connections: work history, education, skills, and their About summary. Use this after search_connections when you need depth on a specific person. Identify them by name, or by linkedin_url for an exact match. A found:false response carries the user's imported-connection count: if no_imported_data is set, nothing was searched, so report the missing import rather than a missing person.

  ConnectorNo auth

• web_search_exaA

  exaA

  Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.

  ConnectorNo auth

• get_schemaA

  studioA

  Returns the base ReoGridJsonDocument schema and an index of advanced features. The base schema already covers cell values, formulas, styling, borders and merges — those need no follow-up call. Call get_feature_spec(feature) only for a name listed in the returned features[] array, passing features[].name verbatim.

  ConnectorNo auth

• linkedin_search_postsA

  captapiB

  Keyword search of public LinkedIn posts — offset cursor, ceiling 50. Costs ~16 credits (0.8/result). Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

  ConnectorNo auth

• search_linkedin_peopleA

  LinkedIn MCP Server (Salesbot)A

  Search LinkedIn people in two backward-compatible modes. EXISTING CONNECTIONS: pass free-text `keywords` with `connectionsOnly: true`; exactly one Classic people search uses `network_distance:[1]`. COMPANY + ROLE: pass `company`, ordered plain `titles`, and preferably the trusted numeric LinkedIn `companyId`. An explicit companyId is applied internally as CURRENT COMPANY (`company:[id]`) while each provider query uses only the plain role as top-level `keywords`; location/network are not sent. Results are retained only when headline/current title semantically matches the requested role, so `count` means relevant role matches rather than raw provider hits. A raw non-matching batch is a miss and title 2 may be tried, with at most two provider POSTs total. A one-title trusted-ID miss may use the second POST for a company+role keyword fallback, guarded by the same role and company checks. Response diagnostics include `search_mode`, `company_filter`, `matched_title`, `tried_titles`, `remaining_titles`, `raw_count`, `relevant_count`, `rejection_summary`, `search_attempts`, and `company_candidates`. This tool does not save contacts. On LINKEDIN_SEARCH_PROTECTED, respect `retry_after_ms`; do not retry in a loop.

  ConnectorNo auth

• get_schema_referenceA

  RationalBloksA

  Get the reference for ADVANCED schema features the templates do not show — read this before adding authorization or derived fields to a schema. Covers: __policy__ (relationship-based read/write authorization with single- and multi-hop membership paths, and the rules that decide whether adopting it is safe — it replaces creator-ownership per table and fails closed on a null link), computed columns (read-only values derived from other columns), __constraints__ (composite uniqueness), __audit__ (append-only audit log), and how user foreign keys are attributed on create.

  ConnectorNo auth

• campaignstack_link_lead_profileA

  campaignstackA

  Attach a platform profile (LinkedIn or X) to an existing PRIVATE lead so one person is sequenceable across channels. Provide at least one of url, externalId, or handle. Fails with PROFILE_ALREADY_LINKED if the profile is attached to a different lead. API-key callers may only link profiles on private (workspace-scoped) leads. Global leads are read-only for user-supplied data.

  ConnectorAPI key

• campaignstack_create_connection_watch_agentA

  campaignstackA

  Create a connection-watch signal agent for a LinkedIn account. The agent monitors the account's newly accepted connections (from activation onward, no backfill) and routes each new connection into an auto-generated welcome workflow (AI-crafted DM → human review → send, plus follow-up rounds). Only one connection watcher may exist per LinkedIn account across all workspaces. The agent is created paused. Use campaignstack_resume_signal_agent to activate it. Advanced path: prefer campaignstack_set_account_watcher, which creates on first enable and pauses or resumes afterwards. Use campaignstack_list_accounts to find account IDs.

  ConnectorAPI key

• campaignstack_send_messageA

  campaignstackA

  Send a LinkedIn message in an existing conversation, optionally with file attachments (public URLs). Takes a conversationRef { platform, id } from campaignstack_list_inbox_conversations. The message is dispatched asynchronously via the runner. The tool returns a messageEntityUrn for tracking. Use campaignstack_get_conversation to check delivery status. Subject to daily send_message budget and business hours gates unless bypassed. When true, bypasses ALL LinkedIn safety limits (daily budget, weekly caps, business hours, account status checks). ⚠️ WARNING: This disables all protections that prevent LinkedIn account restrictions. Use only when you understand the risks and accept that the account may be flagged or restricted by LinkedIn.

  Connector

  Destructive

  API key