Skip to main content
Glama
612,755 tools. Updated 2026-09-26 18:36

"A search for LinkedIn contacts who are decision makers in optical lab manufacturing in Europe" matching MCP tools:

  • Get AI-generated intelligence briefs for each supply chain dimension — energy, materials, transportation, macro, and manufacturing. Each brief provides a narrative analysis of current conditions, key drivers, emerging risks, and recommended watch items. These are not raw data — they are synthesized analytical summaries generated every hour from live data. Designed for decision-makers who need a quick read on each supply chain dimension. Returns structured briefs suitable for executive dashboards, email digests, or Slack channels.
    ConnectorNo auth
  • Get AI-generated intelligence briefs for each supply chain dimension — energy, materials, transportation, macro, and manufacturing. Each brief provides a narrative analysis of current conditions, key drivers, emerging risks, and recommended watch items. These are not raw data — they are synthesized analytical summaries generated every hour from live data. Designed for decision-makers who need a quick read on each supply chain dimension. Returns structured briefs suitable for executive dashboards, email digests, or Slack channels.
    ConnectorNo auth
  • Enrich existing contacts with their full LinkedIn profile data via the connected LinkedIn account (Unipile) — headline, location, current company & position, full experience, education and skills are scraped from each contact's profile URL and saved onto the contact (and merged into profile_data). Use after search_google_xray to flesh out lightly-saved leads. Each contact is a real LinkedIn profile view, so keep batches small; max 8 per call. Returns per-contact enrichment status.
    ConnectorNo auth
  • List inbox conversations across all LinkedIn accounts in the workspace. Call this when the user asks what is in the inbox or who has replied. 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. It returns previews only, not the full thread: use campaignstack_get_conversation for that.
    ConnectorAPI key
  • Get available criteria and their supported values (names and IDs) for target group creation/updates. USE FOR: "what targeting criteria are available?", "what options for [criteria type]?", "supported values for industries/seniority/job functions", "how to search job titles/interests/member groups?", validate criteria before creating target group, get valid IDs for create_target_group. CRITERIA TYPES: 1. LIST-BASED (returns predefined options): - age-ranges: Age range options - company-categories: Company classifications - company-growth-rates: Growth rate ranges - revenues: Revenue ranges - employees: Employee count ranges - industry-taxonomy: Industry codes/names - jobFunctions: Job function categories - seniority: Seniority levels - followed-companies: Company follow options - locations: Geographic data (MANDATORY as FIRST criteria for LinkedIn) - use search_terms for filtering 2. SEARCH-BASED (use search_terms): - job-title: Search job titles (reference_type: LINKEDIN_JOB_TITLES) - member-groups: Search LinkedIn groups (reference_type: LINKEDIN_MEMBER_GROUPS) - member-skills: Search professional skills - interests: Search interests (reference_type: LINKEDIN_INTERESTS) - traits: Search behaviors (reference_type: LINKEDIN_TRAITS) 3. NUMERIC: years-of-experience (0-12, not retrieved via this tool) OPERATION MODES: - List: search_target_group_criteria(channel="LINKEDIN", criteria_type="seniority") - Search: search_target_group_criteria(channel="LINKEDIN", criteria_type="job-title", search_terms=["engineer"], exact_match=false) - Direct: search_target_group_criteria(channel="LINKEDIN", reference_type="LINKEDIN_JOB_TITLES", search_terms=["engineer"]) RESPONSE: Array of {externalId, name}. Use externalId in target group config, show name to users. CHANNEL: Only LINKEDIN supported.
    ConnectorAPI key
  • Search for contacts by title, company, or query. Searches saved Xmagnet contacts first (free, instant), then a profile-first prospecting page of up to 50 profiles (free, emails HIDDEN). Examples: 'CTOs in Denver', 'John Smith at Google', 'VPs of Sales at SaaS startups'. Emails are not included — to reveal one, call find_email for that person (4 credits per verified find). Use load_more_contacts for the next page.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • ifsc-in MCP — Indian bank branch IFSC code lookup via Razorpay's open

  • Indiana BMV MCP — Bureau of Motor Vehicles branches, self-service kiosks, BMV Connect

  • Keyword search across FDA regulations — US Food & Drug Administration rules in 21 CFR. Answers "what FDA regulations cover X", "the FDA regulation / rule about X", "find the FDA requirement for X". Great for topics: good manufacturing practice (GMP / cGMP), quality system regulation, medical device labeling, drug labeling, nutrition facts / food labeling, new drug applications, dietary supplements, cosmetics, biologics, controlled substances, current good manufacturing practice for drugs and devices. Returns matching FDA regulations with citation (21 CFR), heading, excerpt, and source URL. This searches FDA REGULATIONS (regulatory text); for FDA DATA (drug labels, adverse events, recalls) use the openfda tools. Example: fda_search({ query: "medical device labeling" }); fda_search({ query: "good manufacturing practice", limit: 15 }). Keyless.
    ConnectorNo auth
  • List and search contacts in the application, paginated, newest first. Read-only. Filters combine as AND; search matches name, username, email, phone, and platformId; `tags` / `tagIds` keep only contacts carrying at least one of those tags (UTM attribution tags are named "utm: <slug>" — discover them with list_contact_tags). `total` is the full match count, so `limit: 1` counts an audience cheaply. Returns compact contact summaries without variable values — use get_contact for one contact's variables. Remember platformId is unique only per bot, so the same person talking to two bots appears as two contacts.
    ConnectorNo auth
  • Log one or more blood test or biomarker results. use: requested logging/import of lab values or a concrete result to record. Review/interpretation alone: no write. GLUCOSE ROUTING: use this tool for glucose only when it is an actual lab/blood-draw result or part of a reported lab panel. Finger-stick, CGM, home meter, wearable, Apple Health, or Health Connect glucose — including a manual correction to daily glucose — belongs in log_wearable as blood_glucose_mg_dl, not here. REQUIRED WORKFLOW: 1) call list_lab_markers for canonical names and LOINC codes. 2) for each marker the user provides, find the best match and use its canonical marker_name and loinc_code. 3) if no match exists, use the name as stated and omit loinc_code. If the user says they have lab results but hasn't shared them, prompt: "You can paste the text from your lab report PDF, or upload a photo of the results page — I'll parse all the values at once." collection_date: report or explicit user context; missing: ask, never substitute report_date or today. infer: panel_name from matched marker or context. extract: flag (H/L/HH/LL/A), ref_range_low/high and lab_name only when reported. FASTING: fasting_status is only 'fasting' or 'non_fasting' when the user explicitly states it ("I fasted for this", "hadn't eaten"). Never infer it from time of day, a meal mention in notes, or the draw being in the morning — omit the field (leaves it unknown) whenever it wasn't stated. report_date (when the lab reported results, if given separately from the collection date) and draw_id (only when the user is adding a marker to a draw already logged in this conversation) are also optional, omit otherwise. Submit all markers from a single lab visit in one call.
    ConnectorOAuth
  • Search this agency's properties, contacts and deals by free text. Returns typed ids (property:<uuid>, contact:<uuid>, deal:<uuid>) — pass one to fetch for the full record. Windowed, not exhaustive: properties are matched over the 100 most recently updated listings only, then title/address-filtered; deals are matched over the 50 oldest-in-stage OPEN deals only (inquiry/qualified/viewing/offer) — a won, lost or archived deal never appears here. Contacts are matched exhaustively (name/email/phone). For anything outside these windows, or an exhaustive list, call list_properties / list_contacts / list_deals directly. Never returns e-mail or phone — only fetching a contact: id does. `incomplete`, when present, names every kind ("properties"/"contacts"/"deals") whose own read failed — treat those kinds as not searched, not as "no matches".
    ConnectorOAuth
  • General-purpose Google search — returns organic results for any query. Unlike search_google_xray (LinkedIn-only), this searches the entire web. Useful for finding job postings on portals (jobs.cz, prace.cz, profesia.sk, indeed.com), company info, news, or any other web content. Results are NOT saved to contacts — use this for research and discovery. Capped at 4 calls per minute to protect the Serper/Google budget.
    ConnectorNo auth
  • Ask CampaignStack to send one connection request from a LinkedIn account the workspace owner connected. Call this when the user has named one specific person and confirmed sending the request. platform is required ("linkedin"; connection requests are a LinkedIn-only concept, and on other networks you follow instead with campaignstack_follow_profile). Name the person with leadId, which is the supported form; profileUrl is accepted for someone already in the workspace. An optional note is capped at 300 characters by LinkedIn. The workspace's only connected LinkedIn account is used automatically, or pass accountId (campaignstack_list_accounts). This reaches a real person. Before calling it, tell the user exactly who it goes to and read the wording back to them, and wait for an explicit yes. It goes out as soon as this call succeeds: there is no draft state and nothing to recall. One person per call. There is no bulk form, and calling this in a loop over a list is not the supported way to reach a list: put the leads in a lead list with campaignstack_add_leads_to_list and run a workflow over it with campaignstack_trigger_workflow, which paces the sends and applies the review step the workspace configured. Sending is paced by CampaignStack's own daily and weekly limits and business hours, which are set by a human in the app and are not writable from here; see overrideOwnLimits before asking for an exception.
    Connector
    Destructive
    API key
  • Ask CampaignStack to follow a profile from a connected LinkedIn account, so their posts reach the owner's feed. Call this when the user asks to follow a specific person. platform is required (currently "linkedin"). Name the person with leadId, which is the supported form; profileUrl is accepted for someone already in the workspace. The workspace's only connected LinkedIn account is used automatically, or pass accountId (campaignstack_list_accounts). A follow is visible to that person and notifies them; it does not send a connection request, use campaignstack_send_connection_request for that. This reaches a real person. Before calling it, tell the user exactly who it goes to and read the wording back to them, and wait for an explicit yes. One person per call. There is no bulk form, and calling this in a loop over a list is not the supported way to reach a list: put the leads in a lead list with campaignstack_add_leads_to_list and run a workflow over it with campaignstack_trigger_workflow, which paces the sends and applies the review step the workspace configured. Sending is paced by CampaignStack's own daily and weekly limits and business hours, which are set by a human in the app and are not writable from here; see overrideOwnLimits before asking for an exception.
    Connector
    Destructive
    API key
  • Use when your human needs data-center CAPACITY to buy or lease: search DC Hub Capacity Source by size (kW or MW) and/or location (a region such as North America or Europe, a country, a state or a metro). Example: "500 kW anywhere in Europe" → min_kw=500, region=europe. Size is min_kw (in kW) or min_mw (in MW), and it is matched against what a listing can ACTUALLY deliver rather than against its headline total: `contiguous_kw` is the largest single contiguous block available and `min_contract_kw` the smallest chunk the provider will contract, so a colocation with a large total but a small contiguous block does NOT answer a large search, while a large site willing to contract small chunks does; a listing that declares neither is matched on its total. Location is region (a region key or alias) or location (free text matched against each listing's region, country, state and metro); market, state, delivery_type and available_by narrow further. Listings are powered land, powered shells, turnkey capacity and colocation, including sites that are not publicly marketed, for enterprise and agent-led procurement. Returns listing cards (market, region, capacity — with contiguous_kw and min_contract_kw wherever a listing declares them — status and when each listing was last updated) to any caller, plus the filters applied and the program status (live, or upcoming while the first listings are onboarded). Pass slug for one listing: a signed-in human who has accepted the introduction terms sees its specs (signed in means a key with an email bound via claim_free_key then bind_email, or an OAuth connection; accept_capacity_terms records the acceptance the first time); others get the card and the unlock steps. The provider's identity, site and contact are released only after the provider accepts a deal registration, which request_capacity_intro submits, and the listing's disclosure block says whether they have been. Do NOT use for the public facility directory (use search_facilities) or for completed M&A (use list_transactions).
    ConnectorNo auth
  • Remove targeting groups from one or more channels in an existing campaign. Use this tool to detach a named Targeting Group from a channel (e.g. remove "Tech Decision Makers" from LINKEDIN). Channel + targeting-group IDs are resolved internally — you only need the channel type and the targeting group name. (Targeting groups are NOT audiences — to remove a standard audience use remove_audiences_from_campaign.) Works on both campaign structures. On a Channel-First / Native (N×N×N) campaign the targeting group is cleared from its WizNativeAdContainer.targetingGroupId; any container then left with no asset at all is dropped, and on a draft the targeting group is also deleted from the channel's groups; a container left holding ads with nothing to target them is named in the removal message. On Precision/METADATA it uses the legacy group delete. KEYWORDS: remove, delete, targeting group, target group, channel, campaign RESPONSE: - Returns the refreshed campaign state plus a removal_results list with one entry per requested removal recording its success or error. ALWAYS check removal_results — a partial failure (e.g. one of two names not found) still returns normally, so report only what actually came back successful. REQUIRED PARAMETERS: - campaign_id: Campaign ID (numeric identifier) - channel_target_groups: Object mapping channel type → list of targeting group names EXAMPLE: remove_target_groups_from_campaign({ "campaign_id": 42545, "channel_target_groups": {"LINKEDIN": ["Tech Decision Makers"]} })
    Connector
    Destructive
    API key
  • List the people who engaged with THIS user's own LinkedIn posts — their name, headline, LinkedIn profile, how they engaged, what they commented, which posts pulled them in, and ContentIn's ICP fit score. Use it to answer 'who is engaging with me', to find warm contacts, or to see which posts attract the right audience. REACTIONS ARE INCLUDED: a single like creates a lead, so a lead with no comments is completely normal and does not mean something is missing. ABOUT THE SCORE: icp_score is computed BY CONTENTIN, by comparing the person's LinkedIn headline against this user's stated ideal customer profile. It is an estimate from a headline, not verified data about who they are. classified: false with icp_score: null means ContentIn HAS NOT SCORED THIS LEAD YET — report it exactly that way. It does NOT mean the person is a poor fit; those are different claims and only one of them is supported. When icp_score_source is 'user_override' the number is the user's own labelling, not ContentIn's. Results are ordered by ContentIn's computed score when you sort by icp_score, so a lead the user has manually re-labelled keeps its computed position while reporting their number. Page with before/before_id; profiles routinely have thousands of leads.
    ConnectorNo auth
  • Reveal who is behind an anonymous LinkedIn profile link. BILLABLE — about $0.0005 per RESOLVED profile (an unresolvable reference is free) — duplicates in one batch are billed per row, so deduplicate first (Tier 0 list price; your account may pay a different rate — call get_balance for your real prices, and read cost.amount_charged in every response for what was actually spent). Takes the obfuscated links that Sales Navigator leaves in exports, CRMs and ad platforms — `linkedin.com/in/ACwAA…` — plus Sales Navigator lead URLs, bare profile ids and urns, and returns the real profile URL and identity. Pass `profiles` (up to 50) to do a batch in one call. The `id` it returns is the same identifier enrich_lead, generate_email and find_phone accept, so this is the cheap first step before spending on a full record. Returns identity only — no location, company or work history; use enrich_lead for those. The numeric member id is NOT accepted as input (LinkedIn answers 403 to it); it comes back as `linkedin_id`.
    ConnectorOAuth
  • Add saved contacts by contact_id to an existing campaign. Applies tenant-scoped blacklist and duplicate checks, but does NOT send or schedule outreach. For campaigns with a message step, contacts who already received a message from ANOTHER campaign of the same LinkedIn account within the last 30 days are NOT added; they are listed in recently_messaged_details with the reason (error code duplicate_cross_campaign). The response includes scheduled:false and next_tool: prepare_campaign_messages when drafts need approval, otherwise start_campaign. Use list_campaign_queue to inspect progress.
    ConnectorNo auth
  • Rolodex overview: how many contacts the subscriber has, how many have a phone or email, and the top industries and tags. Answers "how many contacts do I have?" and "what industries are my contacts in?" Use get_contact_history to look up specific people.
    ConnectorNo auth
  • Search Latido's public directory of Hungarian wedding vendors and venues (photographers, venues, DJs, florists, caterers, planners…). Use it whenever someone is looking for a supplier for a wedding in Hungary. Filter by category or top-level group, a place name (city, county or "Balaton"), maximum price in HUF, minimum seated capacity, a wedding style, or a date the vendor must be free on. Returns 10 results per page in the directory's own ranking; vendors who have not published a price/capacity/availability are kept (unknown is not a "no"). Each result has a public storefront URL — link to it. Does NOT search vendors who have not published a profile.
    ConnectorNo auth
  • The live Haveno XMR/USD order book, both sides, priced against centralized spot. Each price level carries its cumulative depth, offer count, payment methods and a reversible flag. `asks` are makers selling XMR, so taking one means buying; `bids` are makers buying, so taking one means selling. Offers are advertisements with differing payment methods rather than a matched book, so nothing executes on its own and the best bid can sit at or above the best ask.
    ConnectorNo auth