Skip to main content
Glama
187,055 tools. Last updated 2026-06-10 07:08

"A tool for finding LinkedIn profiles by name and company" matching MCP tools:

  • Enrich a contact with verified work email, phone, LinkedIn, company details, and social profiles. Provide email or full name + company.
    Connector
  • Search the DevMatch index for engineers matching a role or project. Input: pass the richest context you have — (1) a full job description (most common), (2) a synthesized brief after reviewing a company's public repo (README + stack + role needs — preferred over a bare URL when you've evaluated the project), (3) a public github.com repo URL (server fetches README/topics; private repos → paste README as text), or (4) an informal role brief. Longer, more specific input ranks better. Returns up to limit ranked candidates (default 20, max 50) with full inline profiles in structuredContent: login, name, bio, location, followers, html_url, top_repos, top_topics, signals, matched_projects, and contact (recommended_contact, contact.emails[], contact.guessed_emails[], contact.urls{}). MANDATORY: After calling this tool, format your user-facing reply using the REQUIRED OUTPUT FORMAT in server instructions — one block per candidate, every email and every url listed verbatim. Forbidden: collapsing contact to shorthand like "GitHub, LinkedIn, X" or "no email". Do not call get_profile for handles already in these results unless the user asks for deeper detail.
    Connector
  • Find Bluesky accounts by name or handle fragment. Returns ranked profiles with handle, DID, displayName, bio, and follower count. Use before bsky_get_profile or bsky_get_author_feed when you have a name but not a confirmed handle. Supports cursor-based pagination for browsing beyond the first page of results.
    Connector
  • Use for qualitative company discovery (industry, business model, supply chain, competitors, management background). For numerical screening (revenue, margins, ratios, growth rates) use run_sql on company_snapshot instead. Drillr's company knowledge base — searchable across industry classification, product offerings, business model, segment structure, competitive landscape, supply chain, management background, and customer profile. Pass a natural language description (e.g. "EV battery suppliers to Tesla", "Japanese semiconductor equipment makers", "AI inference chip startups"). Returns a structured list of matching companies with context snippets. ONLY for finding a LIST of companies by description.
    Connector
  • Data tool for the current user's saved client context, including client setup status, advertiser profiles, synced account/campaign counts, and any open setup questions. For the user-facing setup UI, prefer render_context_onboarding.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    A
    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.
    Last updated
    MIT
  • A
    license
    -
    quality
    A
    maintenance
    Multilingual name romanization lookup across Chinese, Japanese, Korean, Arabic, Vietnamese, and more. Resolves whether two name spellings refer to the same person — Chan/Chen/陳/陈, Hsu/Xu, Chou/Zhou — across Pinyin, Wade-Giles, Cantonese, Hokkien, and other romanization systems.
    Last updated
    MIT

Matching MCP Connectors

  • linkedin-humblebrag MCP — wraps StupidAPIs (requires X-API-Key)

  • LinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP.

  • Batch-fetch up to 100 profiles by (platform, username) pairs. Use this when the user has a list of handles and you need profile data for all of them at once (e.g., "give me follower counts for these 30 accounts I'm considering" or "which of @a @b @c are real accounts?"). One round-trip beats 30 calls to `get_profile`. Use this for exact batch handle lookup, not semantic discovery. For one exact platform+username pair, use `get_profile`. For partial or fuzzy handle/name input, use `search_creators` or `autocomplete_creators`. Use `semantic_search_creators` only for topical/niche/audience discovery where false-positive semantic matches are acceptable. Examples: - User: "Compare @a, @b, and @c on Instagram" -> use this tool for the exact handle batch. - User: "Give me follower counts for these 30 accounts" -> use this tool. - User: "Find wellness creators in Austin" -> use `semantic_search_creators`, not this tool. The response splits results into `data` (profiles found) and `not_found` (the (platform, username) pairs that weren't recognized). Profiles are returned in no particular order — re-correlate via the platform/username fields if you need to preserve input order.
    Connector
  • Check whether a named individual is banned from acting as a UK company director. Use this tool when asked to check disqualified, banned, or barred directors. Query must be an individual's name (e.g. "Richard Howson") — NOT a company name, which always returns zero results. Returns names, dates of birth, disqualification period snippets, and officer IDs that can be used with disqualified_profile for full details.
    Connector
  • Raw LinkedIn ad analytics data tool for focused follow-up metric pulls at account, campaign, or creative level. Do not use this as the primary response for broad user-facing prompts like 'generate a report', 'show my LinkedIn report', or 'dashboard'; prefer linkedin_render_weekly_group_report for account/ad-account reports, linkedin_render_campaign_analysis for campaign analysis, or linkedin_render_creative_comparison for creative-performance reports. When accountId or campaignId is omitted, recent LinkedIn session selections are used when available.
    Connector
  • Preferred structured LinkedIn creative-metrics tool for one campaign. Compares LinkedIn creative-level performance inside a campaign across trailing windows ending on a specific date. Video campaigns surface video views, view rate, completion rate, and cost per view alongside spend and click metrics. Use this for focused creative follow-up once the campaign has already been identified, instead of falling back to linkedin_get_creatives inventory plus generic CREATIVE analytics. If campaignId is omitted, the most recent LinkedIn campaign from session memory is used when available.
    Connector
  • Run multiple targeted searches and return raw results grouped by section. The caller defines all sections and queries — this tool does not decide what is relevant. Before calling, reason about which topics and data sources matter for this specific company: financial metrics, risk factors, sector-specific macro drivers (e.g. freight rates for shipping, power prices for aluminium smelters), recent press releases, peer context, etc. Formulate one query per section. Each query is run independently as a full hybrid search (dense + sparse + rerank). Results are raw chunks — the caller is responsible for synthesis. For a fully orchestrated due diligence report (AI-planned sections, synthesized narrative), use the Alfred MCP server instead: alfred.aidatanorge.no/mcp IMPORTANT — use 'ticker' on company-specific sections to avoid false positives. Without a ticker filter, documents that merely mention the company (e.g. as a customer or competitor) can rank above actual filings from that company. Omit 'ticker' only for sections where cross-company results are intentional, such as sector macro context or peer comparisons. Args: company: Company name, used for metadata only (not a filter). sections: Up to 8 sections. Example: [ {"name": "financials", "query": "Equinor revenue EBITDA operating profit 2024", "ticker": "EQNR"}, {"name": "risk", "query": "Equinor climate regulatory risk stranded assets", "ticker": "EQNR"}, {"name": "macro", "query": "Brent crude oil price energy sector Norway 2024", "limit": 3}, {"name": "news", "query": "Equinor press release dividend acquisition 2024", "ticker": "EQNR"} ] Returns: Dict with 'company', 'generated_at', and 'sections' — one entry per requested section with its name and results (same format as search_filings). Sections with no results return an empty list.
    Connector
  • Search 500+ quantum computing job listings using natural language. Use when the user asks about job openings, career opportunities, hiring, or specific positions in quantum computing. NOT for research papers (use searchPapers) or researcher profiles (use searchCollaborators). Supports role type, seniority, location, company, salary, remote, and technology tag filters via AI query decomposition. Limitations: quantum computing jobs only, last 90 days, max 20 results. Promoted listings appear first (marked). After finding jobs, suggest getJobDetails for full info. Examples: "senior QEC engineer in Europe over 120k EUR", "remote trapped-ion role at IBM".
    Connector
  • Global Waymarked Trail & Mountain Route Explorer. Queries real-time OpenStreetMap relation networks for designated hiking, biking, and mountain trails anywhere in the world. USE FOR: - "How long does it take to hike up Črna Prst from Podbrdo?" - "Are there any marked mountain paths near this coordinate?" - "Find biking or mountain biking (MTB) trails around this area." - Discovering waymark symbols, route difficulty metrics, and trail networks. CRITICAL INSTRUCTIONS FOR AGENT: - Use this tool instead of standard street routers (`geo-route`) if the destination is a mountain peak, ridge, national park trail, or alpine hut. - Set a small buffer (e.g., 0.005 for 500m, up to 0.02 for ~2km) around coordinates to avoid massive data payloads. - Accept the features returned by this tool as complete. DO NOT iteratively search or run multiple tag queries sequentially. Read the returned trail distances, calculate speed profiles, and answer immediately. NOT FOR: Street-grid driving directions, finding urban shops/cafes, raw city geocoding.
    Connector
  • Search the Companies House register by company name or keyword. Returns a paginated list of matching companies with name, number, status, SIC codes, incorporation date, and registered address. Use company_profile for the full record once you have the company number. Re-call with start_index=start_index+items_per_page to fetch the next page.
    Connector
  • Search the Fryd plant database (3,000+ varieties) by name. Returns a list of matching crops with IDs, descriptions, and whether each is a species or variety. Use the returned crop IDs with get_plant_profile for detailed profiles or check_companion_planting for compatibility checks.
    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
  • Look up a user's public profile by their username (the URL handle, not the display name). Returns display name, account type, verification status, counts of their published books and public annotations, and up to 5 recent published books. Useful for evaluating whether an annotation's author is credible, or for finding more books by the same author.
    Connector
  • Raw data tool for comparing LinkedIn performance across two explicit date windows. Returns validated absolute and percentage deltas for core metrics. Do not call this directly for user-facing prompts like 'generate a report' or 'show a report'; prefer linkedin_render_weekly_group_report for broad account/ad-account reports. Defaults to account scope; pass campaignId to narrow to one campaign. If accountId is omitted, the most recent LinkedIn account from session memory is used when available.
    Connector
  • Searches creatives within a specific LinkedIn Ad Account. This is an inventory/discovery tool for creative IDs, names, statuses, and campaign associations. Do not use it as the primary creative performance tool when a user asks for impressions, clicks, spend, or creative winners/losers; prefer linkedin_compare_creative_performance or linkedin_render_creative_comparison for that. If accountId is omitted, the most recent LinkedIn account from session memory is used when available.
    Connector