Skip to main content
Glama
812,993 tools. Updated 2026-11-20 20:20

"A method for finding people on LinkedIn using their name or company" matching MCP tools:

  • Identify a named employer before using it as a sourcing filter. Pass the company name and any LinkedIn company URL or website the user supplied or that you verified on the web; never invent URLs. Checks PDL's company directory only, does not search for people, and says nothing about how many candidates exist. A supplied LinkedIn URL stays usable even when the directory cannot match it; source and providerStatus tell these outcomes apart. Pass the returned name and slug to build_sourcing_query, or mention the name and LinkedIn URL in an edit_sourcing_query request. Requires OAuth.
    ConnectorOAuth
  • 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" })
    ConnectorNo auth
  • Enrich a person from their email / LinkedIn / name+company / phone using People Data Labs. Returns job title, company, emails, phone numbers, location, and skills. Provide at least one identifier. Example: pdl_person_enrich({ email: "sean@peopledatalabs.com", _apiKey: "your-key" })
    ConnectorNo auth
  • Find a person's phone number by LinkedIn URL, email, or full name and company domain. Covers professional contacts only: people in their role at a company, not private individuals. Charges 2 credits only when a phone number is found.
    ConnectorOAuth
  • A person's public LinkedIn profile: name, headline, the companies and schools on it, location, followers and their latest posts, for preparing a conversation. person: the profile's link, or the name with the company. Works once the account's owner has switched on finding people in Puley's Account settings. Saved in the user's Puley history.
    ConnectorOAuth
  • A person's public LinkedIn profile: name, headline, the companies and schools on it, location, followers and their latest posts, for preparing a conversation. person: the profile's link, or the name with the company. Works once the account's owner has switched on finding people in Puley's Account settings. Saved in the user's Puley history.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    MCP server for the Mamba Labs People Finder & Email Verifier actor on Apify. Give it a company domain, name or LinkedIn URL and it returns the people at that company who match your role, seniority and department filters, each as a structured contact record with an optional verified business email.
    1
    121 npm
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    MCP server for LinkedIn Company Page administration. Enables reading analytics, managing posts, editing page details, growing followers, and bridging personal profile for employee advocacy workflows.
    24
    MIT

Matching MCP Connectors

  • Find LinkedIn people by name, title, employer or school. Paid, on Apify's hosted MCP.

  • LinkedIn company pages as JSON: industry, size, HQ, followers, and specialties, via hosted MCP.

  • Find people on stage across every event: name, title, company, LinkedIn, talk, role. Filter by company (name or domain), title, persona, sector, country, dates.
    ConnectorNo auth
  • Search LinkedIn for people by keywords: a job title, skill, company or industry, optionally in a place. Returns name, current role and company, location and profile link. Good for finding prospects, hires or experts.
    ConnectorOAuth
  • The people at a company who hold a role: name, job title, city and LinkedIn profile, to find who to talk to. company: its website or name. role: a job title or department, such as head of marketing. limit: 3 to 25. A work email is shown where it has been checked. Works once the account's owner has switched on finding people in Puley's Account settings. Saved in the user's Puley history.
    ConnectorOAuth
  • The people at a company who hold a role: name, job title, city and LinkedIn profile, to find who to talk to. company: its website or name. role: a job title or department, such as head of marketing. limit: 3 to 25. A work email is shown where it has been checked. Works once the account's owner has switched on finding people in Puley's Account settings. Saved in the user's Puley history.
    ConnectorOAuth
  • For a list of companies (e.g. from search_crunchbase or get_pitchbook_profiles): finds people with a given role on LinkedIn and their work email on the company website domain.
    ConnectorNo auth
  • 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.
    Connector
    Destructive
    No 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
  • Change one of the merchant's draft orders, as the order page does: its shipping method, 48H fulfillment on or off, its reference_id, or any of them. Its address and line items have tools of their own. 48H (made and shipped within 2 business days, for an added fee) needs at least one item on the order that offers it, and changes which methods the order can use. A method the order's address and items don't ship with is refused, naming the ones they do. reference_id is the merchant's own id for the order: one another of their orders has, unless it was cancelled, is refused, naming that order. A submitted or rejected order needs move_order_to_draft first. Returns the methods the order ships with now, none until every line item has a product, and its new total.
    Connector
    Destructive
    API key
  • Use this when the user names one company and you need to pin down exactly which company it is. Returns its name, website domain, LinkedIn page and logo. Send at least one of name, domain or linkedinUrl; when several are sent only the most precise is looked up (LinkedIn URL, then domain, then name). A bare name resolves to the best-known company of that name, so send a domain for a common name. When nothing matches, the status is not_found: it never guesses. Free.
    ConnectorOAuth
  • Find people on LinkedIn by keywords and filters. The right tool when you have a name, role, or 'who is the X at Y' question without a profile URL. Pass keywords (free text: name, title, or both) and any of first_name, last_name, title, school, current_company, past_company. If keywords is omitted it is derived from the name or title filters; school or company filters alone are rejected with INVALID_INPUT, so include keywords with those. Company filters accept a company name, slug, numeric id, or URN. current_company names are matched by LinkedIn's own company search: typo-tolerant and fuzzy, so results can include people whose headline merely mentions the company; when you need exact filtering, pass the numeric id or URN (linkedin_get_company returns both). past_company names are resolved to an id for you. Costs 10 credits including the first 10 results; each further 10 results add 1 credit (limit max 30; trial keys max 10). A cursor page is a NEW call priced the same way by its own limit, so one limit=30 call is much cheaper than three limit=10 pages; prefer a larger limit over paginating. Do NOT combine a past_company NAME or a company-URL filter with limit=30: resolving those spends one of the call's three internal fetches, so that combination is rejected; keep limit<=20 with them or pass the numeric id. current_company names never spend a fetch, so they combine with any limit. Returns name, position, location, urn, public_identifier per result, a cursor for the next page, and total_matches. Results with is_anonymous=true are private profiles; do not pass them to linkedin_get_profile. For one known person with a URL/slug, call linkedin_get_profile directly instead.
    ConnectorOAuth
  • Fetch one company's LinkedIn page: name, description, industry, employee count, headquarters, website, founding year, specialities, and the URN/numeric id you need for linkedin_search_people company filters. identifier accepts a company URL, the slug after /company/ (e.g. 'microsoft'), or a website domain like 'microsoft.com'; numeric ids and URNs are search-filter inputs, not fetch identifiers. Domains are resolved to a company and verified against that company's website: a domain identifier always QUOTES base+4 credits (set max_credits accordingly), and the 4-credit resolution surcharge is refunded at settlement when the domain was resolved before, so known domains settle at the base price. A domain that cannot be verified to a company returns INVALID_INPUT with the closest matches instead of a guessed company. Costs 4 credits base. Do not guess a slug from a brand name: slugs are vanity strings and a famous name can belong to an unrelated company's page (linkedin.com/company/anthropic is a small investment fund, not the AI lab). When you only know the company's name, pass its website domain instead -- the verified form -- and sanity-check the returned industry and description against what you expected. This tool does not search by name: if you only have an approximate company name, use linkedin_search_people's current_company filter with keywords (names are matched natively there) or give the exact slug. For the company's posts, use linkedin_get_posts with the same identifier (URL, slug, or website domain all work there too).
    ConnectorOAuth
  • Screen ONE natural PERSON's full name against sanctions (OFAC, EU, UN) and PEP lists. IMPORTANT — this is a PERSON tool only. Do NOT pass a company name, an organisation number (orgnr), or any non-person string here. For company-level AML risk use `firmaradar_get_aml_score` (by orgnr); to screen a company's owners/officers, first resolve the people via `firmaradar_get_company_roles` / `firmaradar_get_company_ownership`, then screen each PERSON name with this tool. Compliance-critical: PII-sensitive, requires a signed DPA and a legitimate purpose per call (free-text `purpose` parameter). Audit-logged for 60 months. Rate-limited to 50 calls / 30 min per API-key. Returns structured hits with category, sources, and match-ratio (default min 0.85).
    ConnectorNo auth
  • Retrieve the name and description of the company behind a job, by job ID. Use this tool when users want more detail about a company than search_jobs/get_job_details return (e.g. after finding a job and wanting to know more about the company that posted it). DO NOT use for: searching/discovering companies or jobs by keyword (use search_jobs instead). LLM USAGE INSTRUCTIONS: - The typical flow is: search_jobs to find jobs -> user picks one -> offer to look up the company -> if the user agrees, call this tool with that same job_id (the same guid used for get_job_details; no separate lookup step is needed first). - Do not call this automatically right after get_job_details; ask the user first unless they already explicitly asked for company details. - Not every company has published an employer branding profile, and some profiles are marked not visible by the company. When that happens this tool does NOT raise — it returns a Company with `message` set and empty name/desc. Relay that message to the user (e.g. "Looks like that company hasn't published a public profile.") rather than treating it as an error. Args: job_id: The unique identifier of the job whose company to look up (required). This must be the job's `guid` field from a search_jobs result, NOT its `id` field — `id` is a different, internal identifier that this tool does not accept. Returns: Company: Contains: - name: The company name (empty if message is set) - desc: The company description (empty if message is set) - message: Set instead of name/desc when there is no visible company profile to show; None when name/desc are populated Raises: Exception: If the job is not found, an API call itself fails (network error, non-200 response, GraphQL errors), or input validation errors occur
    ConnectorNo auth
  • Delete EVERY object of one type from the user's graph, however many there are: what to reach for when they ask to clear out a whole category ('delete all my HubSpot contacts') rather than one record. Pass import_id instead to delete everything one import added (its contacts, companies, notes and files, the uploaded file and the import itself); imports are graph objects of type 'import_run'. Pass source 'linkedin_import' instead to delete every connection a LinkedIn export loaded and the people made from them. Deleting one object is delete_graph_object instead. This delete is permanent, and at this scale it is the only kind that helps: a synced portal can be millions of records. Use only when the user explicitly asked for these to go, never on your own initiative, and name one type, import or source per call. In chat this tool deletes nothing: it counts the records and returns what to tell the user, and their click starts the deletion.
    Connector
    Destructive
    No 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