Skip to main content
Glama
510,057 tools. Updated 2026-09-03 19:32

"A search for finding people using Google, LinkedIn, and other databases" matching MCP tools:

  • Search people on LinkedIn by title, current company and location. Pass `company` (a company NAME like 'Škoda Auto') to filter to people who CURRENTLY work there — without it the search returns random people matching only the title. Returns JSON `{ count, results, company_filter }` where each item in `results` has: `linkedin_url`, `name`, `headline`, `company`, `location`, `public_id`, `network_distance` (read `linkedin_url` for the profile URL — NOT `profiles`/`url`). `company_filter.mode` is `current_company` when the name resolved to LinkedIn's native filter, or `keyword_fallback` when it could not. It does not save them as Salesbot contacts. For each profile you want to keep or add to a campaign, call upsert_linkedin_contact with its `linkedin_url` to obtain a contact_id. Pass either `location` (human name like 'Praha', 'Berlin', 'Czechia') or `locationId` (raw LinkedIn geo ID).
    Connector
  • 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.
    Connector
  • 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.
    Connector
  • Which growth data sources and distribution channels are connected: GA4 and Search Console (the measurement behind SEO and outcomes), Google Business Profile, and the LinkedIn / Reddit posting channels. Each row carries an honest state: connected, not_connected, or not_available with the reason it is shut on this account. Read before start_connection so you never offer a connection that cannot be made. Read-only, free.
    Connector
  • 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
    Connector
  • 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.
    Connector

Matching MCP Servers

  • A
    license
    B
    quality
    B
    maintenance
    An MCP server that gives AI agents a private, durable memory of people, providing a personal people graph in PostgreSQL with tools to search, remember, and connect people, plus imports from LinkedIn, Google Contacts, and WhatsApp, and a browser UI.
    11
    1
    MIT

Matching MCP Connectors

  • google search: google web search api, web, images, videos, news, music, favicon, proxy, audio.

  • Scrape Google search results with SERP data, ads, and knowledge panels

  • Job/opportunity search with the full filter set. Location filtering works: pass `locations` a LinkedIn geo id (e.g. 101570771 for Tel Aviv-Yafo) — see that parameter for how to find one, and note it is an EXACT match, so use a city id rather than a country id. Still id-typed and not yet usable: titles, industries, functions, benefits, commitments. Offset-paginated. data.jobs[].id is the opportunityEntityId consumed by /jobs/details-v2, /jobs/similar, /jobs/people-also-viewed, /jobs/hiring-team. (Costs 10 Zooq credits.)
    Connector
  • List supported Google Maps place type values for search filters. Returns place_types as a string array. Use a value with place_type on google-maps.search or google-maps.nearby_search. Cost = 1 token.
    Connector
  • 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.
    Connector
  • Exact Google Ads search volume for `<keyword>` — Google's own monthly search-volume numbers (plus competition and CPC) from the Ads API, for up to 10 keywords. Use when you specifically need Google Ads figures; for general SEO volume + keyword difficulty, prefer seo_keyword_overview (cheaper). Example: seo_keyword_google_ads_volume({ keywords: ["running shoes"], location_code: 2840, _apiKey: "your-base64-key" })
    Connector
  • 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).
    Connector
  • Search patient discussion threads on community.navmds.com — the NavMDs forum where people discuss recovery timelines, what procedures actually cost them, choosing a surgeon, and what to expect. Use this for lived-experience questions ('what is rhinoplasty recovery like', 'how much did people actually pay for a tummy tuck', 'how do I pick a surgeon') where the doctor-directory tools can't help. Returns thread titles, categories, excerpts and canonical URLs; pass an id to get_community_thread for the full discussion. Community posts are patient discussion, not medical advice.
    Connector
  • Job/opportunity search with the full filter set. Location filtering works: pass `locations` a LinkedIn geo id (e.g. 101570771 for Tel Aviv-Yafo) — see that parameter for how to find one, and note it is an EXACT match, so use a city id rather than a country id. Still id-typed and not yet usable: titles, industries, functions, benefits, commitments. Offset-paginated. data.jobs[].id is the opportunityEntityId consumed by /jobs/details-v2, /jobs/similar, /jobs/people-also-viewed, /jobs/hiring-team. (Costs 10 Zooq credits.)
    Connector
  • List Search Console properties for this account. Returns Vee3-managed domains plus sites added with google-search-console.add_site. Call this to discover sites, then omit site_url on later calls to use the default property, or pass an exact site_url from this response. If no properties appear, add a site with google-search-console.add_site or register a domain with domains.register. Cost = 5 tokens.
    Connector
  • The SaaS applications the customer's own Google or Microsoft tenant says its people actually use, with how many distinct users were seen and whether Fallax ships a lure that impersonates that app. The single best predictor of whether a simulation is plausible, and the right input when suggesting what to simulate next. Returns nothing unless the workspace turned app discovery on.
    Connector
  • Search across ALL string properties of ALL nodes in a deployed graph using free-text queries. Unlike search_graph_nodes (which filters by specific property), this searches every text field at once. Perfect for finding knowledge when you don't know which property contains the answer. Example: query "quantum" searches name, description, summary, notes, and all other string fields. Returns nodes with _match_fields showing which properties matched. Optionally filter by entity_type to narrow results.
    Connector
  • Get the profile of one person in crypto by id: name, description or bio, teams_count, positions held, and linked projects plus social and code accounts. Use for 'who is Vitalik Buterin', 'background on Charlie Lee', 'projects tied to this founder'. Find the personId first with search or resolveId using type 'people'; this tool needs the exact id, not a name. Read-only. Params: personId (required) is a canonical person id such as 'vitalik-buterin' or 'satoshi-nakamoto'; an unknown id returns not found. No API key required.
    Connector
  • Run a Google search from a chosen country and return organic results, with optional AI Overview extraction (include.aioverview) and People-Also-Ask AI answers (include.paaAioverview). Two modes: structured (query + country, with optional location/uule/pages) or url (a complete google.com/search URL that owns query, location, and pagination). Supports desktop, mobile, iOS, and Android emulation and multi-page results.
    Connector
  • Skill catalog search by name (partial match) — skills only, despite the endpoint name. Page-paginated. Use to find a skill's skl_ id or normalized_name for the /search/people skills filter. (Costs 10 Zooq credits.)
    Connector
  • Enrich a company from its name or domain using People Data Labs. Returns size, employee count, industry, founding year, location, LinkedIn, and website. Provide a name and/or website. Example: pdl_company_enrich({ website: "peopledatalabs.com", _apiKey: "your-key" })
    Connector