> ## Documentation Index
> Fetch the complete documentation index at: https://composio-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Explorium MCP

> Explorium AgentSource MCP provides agents with structured company, professional, contact, firmographic, technographic, and business-event data.

![Explorium MCP logo](https://mintcdn.com/composio-preview/r7CO9m4_UWMVFnU7/images/toolkits/explorium_mcp.svg?fit=max\&auto=format\&n=r7CO9m4_UWMVFnU7\&q=85\&s=5b4c9d3cf0351df2f10d2bbf387563cb)

* **Category:** model context protocol
* **Auth:** API\_KEY
* **Composio-managed OAuth available?** N/A
* **Tools:** 12
* **Triggers:** 0
* **Slug:** `EXPLORIUM_MCP`
* **Version:** 20261018\_00

## Tools

> [accordion] Autocomplete
>
> **Slug:** `EXPLORIUM_MCP_AUTOCOMPLETE`
>
> Provides standardized parameter values that MUST be used in fetch-entities filter operations and bombora-intent enrichment. This tool should be called FIRST before searches or enrichments that require these specific field values.
>
> **Query rules (critical):**
>
> * Pass exactly one concept per call: a single word or short phrase (≤100 characters).
> * Never pack comma-separated or space-joined lists (e.g. "defense, aviation, medical devices") into one query — that fails.
> * For multiple concepts, call autocomplete once per concept and merge the returned values.
>
> **Supported Fields (call this tool to get valid values):**
>
> * `naics_category`: NAICS industry codes
> * `linkedin_category`: LinkedIn industry categories
> * `company_tech_stack_tech`: Specific technologies
> * `job_title`: Job titles
> * `interests`: Professional interests for prospect filters
> * `skills`: Professional skills for prospect filters
> * `business_intent_topics`: Bombora intent taxonomy strings for fetch filters and enrich-business bombora-intent parameters.topics (prefer ≥12 topics)
>
> **Fields NOT Requiring Autocomplete:** These fields have fixed enum values or use standard codes directly:
>
> * `country_code`: Use ISO Alpha-2 codes (e.g., "US", "IL")
> * `company_country_code`: Use ISO Alpha-2 codes (e.g., "US", "IL")
> * `region_country_code`: Use ISO 3166-2 codes (e.g., "US-NY", "IL-TA")
> * `company_region_country_code`: Use ISO 3166-2 codes (e.g., "US-NY", "IL-TA")
> * `website_keywords`: Use free-text keywords directly
> * Enum fields: See available values in fetch-entities description
>
> **Technical Requirement:** Search operations using autocomplete-required filters will fail without valid values from this tool first.
>
> **Search Tips:**
>
> * For SaaS companies: Use the keyword 'software'
>
> **Returns:** List of valid, standardized values that must be used in search filter parameters
>
> #### Input Parameters
>
> **field** `string ("naics_category" | "linkedin_category" | "company_tech_stack_tech" | "job_title" | "interests" | "skills" | "business_intent_topics")` *required*
>
> The field to autocomplete. Use only fields listed here. Never use autocomplete for a field not included in this list. If a field is not listed, it either has a fixed set of allowed values (e.g., `NumberOfEmployeesRange`), or should be used directly as-is with no autocomplete.
>
> **query** `string` *required*
>
> One short concept only: a single word or short phrase (max 100 characters). Never pass comma-separated or space-joined lists of industries, topics, titles, or tech — call autocomplete once per concept and merge the returned values.

> [accordion] Enrich-business
>
> **Slug:** `EXPLORIUM_MCP_ENRICH_BUSINESS`
>
> Enriches business data enrichment calls. Requires business IDs as input.
>
> **Input Requirements:**
>
> * business\_ids: Array of Explorium business IDs (from match-business or fetch-businesses)
> * enrichments: enrichment types to retrieve
> * parameters: Optional settings for specific enrichments
>
> **IMPORTANT: For comprehensive company information requests, include ALL relevant enrichments in a single call** (e.g., for "tell me about this company" use multiple enrichments: firmographics, technographics, funding-and-acquisitions, workforce-trends, linkedin-posts to provide complete intelligence)
>
> **Available Enrichments:**
>
> * **firmographics**: Basic company info (name, description, website, location, industry, size, revenue)
> * **technographics**: Complete technology stack used by the business
> * **company-ratings**: Employee satisfaction and company culture ratings
> * **financial-metrics**: Financial data for public companies only (requires date parameter in ISO format: "2024-01-01T00:00")
> * **funding-and-acquisitions**: Funding history, investors, IPO, acquisitions
> * **challenges**: Business challenges and risks from SEC filings
> * **competitive-landscape**: Market position and competitors from SEC filings
> * **strategic-insights**: Strategic focus and value propositions from SEC filings
> * **workforce-trends**: Department composition and hiring trends
> * **linkedin-posts**: Company LinkedIn posts and engagement metrics
> * **website-changes**: Website content changes over time
> * **website-keywords**: Search for specific keywords on company websites (requires keywords parameter: array of terms - comma-separated terms within strings enable AND logic)
> * **webstack**: Website-specific technologies and web infrastructure components detected on company websites
> * **company-hierarchies**: Corporate hierarchy including parent company, ultimate parent, subsidiaries, and full organization tree (JSON format)
> * **bombora-intent**: Company-level buying intent from Bombora weekly data (surging research topics). Always call autocomplete first with field=business\_intent\_topics to resolve topics. Prefer ≥12 topics for meaningful level\_of\_intent. Returns intent\_topics (score ≥ threshold), level\_of\_intent, topic\_count, date\_stamp. Interpret level\_of\_intent: In-Depth Research (>25% topics surging), Active Research (5–25%), Early Research (\<5%). If topic fields are null, the company has no available intent data for that week.
>
> **Parameters:**
>
> * date: ISO 8601 format for financial-metrics (e.g., "2024-01-01T00:00")
> * keywords: Array of search terms for website-keywords
> * topics: Array of Bombora "category: topic" strings for bombora-intent (from autocomplete)
> * min\_score: Optional integer > 60 for bombora-intent (default 60 when omitted)
>
> **Alternative Tools:**
>
> * For finding specific employees or company leadership information, use fetch-prospects with job\_level filters (e.g., "c-suite" for c-level) instead of firmographics or strategic-insights enrichments
>
> **Returns:** Combined structured data from all requested enrichments
>
> **Example:**
>
> ```text theme={null}
> {
>   "business_ids": ["8adce3ca1cef0c986b22310e369a0793", "340c8040bd50cbab9c7df718bbe51cc9"],
>   "enrichments": ["firmographics", "technographics", "funding-and-acquisitions"],
>   "parameters": null
> }
> ```
>
> #### Input Parameters
>
> **parameters** `object`
>
> **enrichments** `array` *required*
>
> List of enrichment types to run in parallel
>
> **business\_ids** `array` *required*
>
> List of Explorium business IDs from match\_businesses

> [accordion] Enrich-prospects
>
> **Slug:** `EXPLORIUM_MCP_ENRICH_PROSPECTS`
>
> Enriches prospect data using up to 3 parallel enrichment calls. Requires prospect IDs as input.
>
> **Input Requirements:**
>
> * prospect\_ids: Array of Explorium prospect IDs (from match-prospects or fetch-prospects)
> * enrichments: 1-3 enrichment types to retrieve
> * parameters: Optional settings for specific enrichments
>
> **IMPORTANT: For comprehensive prospect information requests, include ALL relevant enrichments in a single call** (e.g., for "tell me about this person" use multiple enrichments: profiles, contacts, linkedin-posts to provide complete intelligence)
>
> **Available Enrichments:**
>
> * **contacts**: Professional and personal email addresses, phone numbers; optional `parameters.contact_types` as `["email"]`, `["phone"]`, or `["email","phone"]` (omit to request both)
> * **linkedin-posts**: Post content, engagement metrics, creation dates
> * **profiles**: Full name, demographics, location, role details, work experience, education
>
> **Returns:** Combined structured data from all requested enrichments
>
> **Example:**
>
> ```text theme={null}
> {
>   "prospect_ids": ["edf268ac410ff3ba9ca9cc67b065664f38201984", "5b486640efabe6f8bb8cf446e80169ba4a1c5ad8"],
>   "enrichments": ["contacts", "profiles"],
>   "parameters": { "contact_types": ["email"] }
> }
> ```
>
> #### Input Parameters
>
> **parameters** `object`
>
> **enrichments** `array` *required*
>
> List of enrichment types to run in parallel
>
> **prospect\_ids** `array` *required*
>
> List of Explorium prospect IDs from match\_prospects or fetch\_prospects

> [accordion] Fetch-businesses
>
> **Slug:** `EXPLORIUM_MCP_FETCH_BUSINESSES`
>
> Searches for businesses using filter criteria. Supports combining multiple filters in a single request for optimal performance.
>
> **Filter Types:**
>
> **Enum-Based Filters** (use values directly from the lists below):
>
> * `company_revenue`: List\[CompanyRevenue] - Revenue range in USD
>   * Available values: "0-500K", "500K-1M", "1M-5M", "5M-10M", "10M-25M", "25M-75M", "75M-200M", "200M-500M", "500M-1B", "1B-10B", "10B-100B", "100B-1T", "1T-10T", "10T+"
> * `company_age`: List\[CompanyAge] - Company age in years
>   * Available values: "0-3", "3-6", "6-10", "10-20", "20+"
> * `company_size`: List\[NumberOfEmployeesRange] - Employee count range
>   * Available values: "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10001+"
> * `number_of_locations`: List\[NumberOfLocations] - Number of offices
>   * Available values: "0-1", "2-5", "6-20", "21-50", "51-100", "101-1000", "1001+"
>   * `company_tech_stack_category`: List\[WebTechCategory] - Broader technology categories
>   * Available values:\
>     "Healthcare And Life Science","Technology","Marketing","E-commerce","Devops And Development","Programming Languages And Frameworks",\
>     "Testing And Qa", "Platform And Storage","Health Tech","Business Intelligence And Analytics","Operations Management","Customer Management",\
>     "Hr","Industrial Engineering And Manufacturing","Product And Design","Sales","It Security","It Management","Other","Operations Software",\
>     "Finance And Accounting","Computer Networks","Collaboration","Communications","Business","Productivity And Operations"
>
> **Autocomplete-Required Filters** (standardized values MUST be obtained from autocomplete tool FIRST):
>
> * `linkedin_category`: LinkedIn industry categories - REQUIRES autocomplete
> * `company_tech_stack_tech`: Specific technologies - REQUIRES autocomplete
> * `naics_category`: NAICS industry codes - REQUIRES autocomplete
> * `business_intent_topics`: Object \{topics: string\[], negate?: boolean} - Intent topic strings (e.g., "Security:Cloud Security", "HR:Employee Benefits"). Max 20 topics. Set negate=true to exclude matching companies.
> * `city_region`: City regions (USA only) - REQUIRES autocomplete
>
> **Event-Based Filters** (use enum values directly, no autocomplete needed):
>
> * `events`: Object with "values" (array of event types from fixed enum) and "last\_occurrence" (days: 30-90)
>
>   * This filter identifies businesses that have experienced specific events within a time window
>   * After fetching businesses with event filters, use fetch-businesses-events to get detailed event information
>
>   **BUYING INTENT (CRITICAL FOR SALES PROSPECTING)**
> * When user wants to find potential customers/prospects for what they're selling
> * Use business\_intent\_topics filter (requires autocomplete)
> * ExampleKeywords: "selling to", "need", "looking for", "interested in buying", "prospects for"
>
> **Boolean Filters** (true/false/null):
>
> * `has_website`: boolean or null - Set to true for businesses with websites, false for businesses without websites, or null to include all
> * `is_public_company`: boolean or null - Set to true for publicly traded companies, false for private companies, or null to include all
>
> **Direct-Use Filters** (use standard codes directly, no autocomplete needed):
>
> * `country_code`: ISO Alpha-2 country codes (e.g., "US", "IL")
> * `region_country_code`: ISO 3166-2 region codes (e.g., "US-NY", "IL-TA")
>
> **Technical Constraints:**
>
> * `linkedin_category` and `naics_category` are mutually exclusive
> * `region_country_code` and `country_code` are mutually exclusive
> * **CRITICAL:** Search requests using linkedin\_category, company\_tech\_stack\_tech, or naics\_category filters will fail without standardized values from autocomplete tool obtained first
>
> **Returns:** Business records including business IDs (usable with enrich-business or fetch-businesses-events)
>
> **Performance Note:** All applicable filters can be combined in a single request
>
> #### Input Parameters
>
> **page** `number`
>
> The page number to return
>
> **size** `number`
>
> The number of businesses to return
>
> **filters** `object` *required*
>
> **page\_size** `number`
>
> The number of businesses to return per page - recommended: 5
>
> **tool\_reasoning** `string`
>
> The original user query that prompted this workflow, in EXACT WORDS. Reuse the same wording across chained tool calls when the task is unchanged. Do not replace it with a per-step rationale or unrelated PII. Maximum 2000 characters. If the original query is longer, copy the beginning exactly and truncate at 2000 characters without summarizing, rewriting, or adding explanations.

> [accordion] Fetch-businesses-events
>
> **Slug:** `EXPLORIUM_MCP_FETCH_BUSINESSES_EVENTS`
>
> Retrieves detailed business-related events from the Explorium API in bulk.
>
> **Use Cases:**
>
> * Get detailed event information after filtering businesses using the events filter in fetch-businesses
> * Research a company's complete event history with specific event types and timestamps
> * Analyze timing and details of funding rounds, partnerships, office changes, etc.
>
> **Workflow:**
>
> 1. Use fetch-businesses with events filter to find businesses that experienced specific events
> 2. Use this tool (fetch-businesses-events) to get detailed event information for those businesses
>
> **Note:** For events related to role changes or people movements, use the prospects events tool instead.
>
> #### Input Parameters
>
> **event\_types** `array` *required*
>
> Business event types to fetch.
>
> **business\_ids** `array` *required*
>
> Explorium business IDs to fetch events for.
>
> **timestamp\_from** `string` *required*
>
> ISO format datetime string or date in format YYYY-MM-DD

> [accordion] Fetch-businesses-statistics
>
> **Slug:** `EXPLORIUM_MCP_FETCH_BUSINESSES_STATISTICS`
>
> Fetch aggregated insights into businesses by industry, revenue, employee count, and geographic distribution.
>
> #### Input Parameters
>
> **filters** `object` *required*
>
> **tool\_reasoning** `string`
>
> The original user query that prompted this workflow, in EXACT WORDS. Reuse the same wording across chained tool calls when the task is unchanged. Do not replace it with a per-step rationale or unrelated PII. Maximum 2000 characters. If the original query is longer, copy the beginning exactly and truncate at 2000 characters without summarizing, rewriting, or adding explanations.

> [accordion] Fetch-prospects
>
> **Slug:** `EXPLORIUM_MCP_FETCH_PROSPECTS`
>
> Searches for prospects (employees) using detailed filter criteria. Supports combining multiple filters in a single request for optimal performance.
>
> **Use Cases:** Finding people in specific roles at companies:
>
> * "Who is the CTO at Google?"
> * "Find engineers at Microsoft"
> * "Show me sales directors at Apple"
>
> **Data Characteristics:**
>
> * Provides verified, structured professional data
> * Returns prospects with detailed role information
>
> **Filter Types:**
>
> **Enum-Based Filters** (use values directly from the lists below):
>
> * `job_level`: List\[JobLevel] - Seniority level of the job
>   * Available values: "c-suite", "manager", "owner", "senior non-managerial", "partner", "freelancer", "junior", "director", "board member", "founder", "president", "senior manager", "advisor", "non-managerial", "vice president"
> * `job_department`: List\[JobDepartment] - Department or function in the organization
>   * Available values: "administration", "healthcare", "partnerships", "c-suite", "design", "human resources", "engineering", "education", "strategy", "product", "sales", "r\&d", "retail", "customer success", "security", "public service", "creative", "it", "support", "marketing", "trade", "legal", "operations", "real estate", "procurement", "data", "manufacturing", "logistics", "finance"
> * `company_size`: List\[NumberOfEmployeesRange] - Employee count range
>   * Available values: "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10001+"
> * `company_revenue`: List\[CompanyRevenue] - Revenue range in USD
>   * Available values: "0-500K", "500K-1M", "1M-5M", "5M-10M", "10M-25M", "25M-75M", "75M-200M", "200M-500M", "500M-1B", "1B-10B", "10B-100B", "100B-1T", "1T-10T", "10T+"
> * `total_experience_months`: RangeInt - Experience in months (e.g., \{"gte": 12, "lte": 120})
> * `current_role_months`: RangeInt - Months in current role (e.g., \{"gte": 6, "lte": 24})
> * `company_age`: List\[CompanyAgeRange] - Years since company founding
>   * Available values: "0-3", "3-6", "6-10", "10-20", "20+"
> * `company_number_of_locations`: List\[NumberOfLocations] - Number of office locations the company operates
>   * Available values: "0-1", "2-5", "6-20", "21-50", "51-100", "101-1000", "1001+"
>
> **Boolean Filters** (true/false/null):
>
> * `has_email`: literal true or null - Filter to include only prospects with verified email addresses
> * `has_phone_number`: literal true or null - Filter to include only prospects with available phone numbers
> * `has_website`: boolean or null - Set to true for prospects from companies with websites, false for prospects from companies without websites, or null to include all
> * `is_public_company`: boolean or null - Set to true for prospects from publicly traded companies (with stock tickers), false for private companies, or null to include all
>
> **Autocomplete-Required Filters** (standardized values MUST be obtained from autocomplete tool FIRST):
>
> * `linkedin_category`: LinkedIn industry categories - REQUIRES autocomplete
> * `job_title`: Job titles - REQUIRES autocomplete
> * `interests`: Professional interests - REQUIRES autocomplete
> * `skills`: Professional skills - REQUIRES autocomplete
> * `naics_category`: NAICS industry codes - REQUIRES autocomplete
> * `business_id`: Business IDs - REQUIRES match-business or fetch-businesses
>
> **Direct-Use Filters** (use standard codes directly, no autocomplete needed):
>
> * `country_code`: ISO Alpha-2 country codes (e.g., "US", "IL")
> * `company_country_code`: ISO Alpha-2 country codes (e.g., "US", "IL")
> * `region_country_code`: ISO 3166-2 region codes (e.g., "US-NY", "IL-TA")
> * `company_region_country_code`: ISO 3166-2 region codes (e.g., "US-NY", "IL-TA")
>
> **Technical Constraints:**
>
> * `linkedin_category` and `naics_category` are mutually exclusive
> * `region_country_code` and `country_code` are mutually exclusive
> * `company_region_country_code` and `company_country_code` are mutually exclusive
> * **CRITICAL:** Search requests using linkedin\_category, job\_title, interests, skills, naics\_category, or business\_id filters will fail without standardized values obtained first from their respective tools
>
> **Returns:** Prospect records including prospect IDs (usable with enrich-prospects or fetch-prospects-events)
>
> **Performance Note:** All applicable filters can be combined in a single request
>
> #### Input Parameters
>
> **page** `number`
>
> The page number to return
>
> **size** `number`
>
> The number of prospects to return
>
> **filters** `object` *required*
>
> **page\_size** `number`
>
> The number of prospects to return per page - recommended: 5
>
> **tool\_reasoning** `string`
>
> The original user query that prompted this workflow, in EXACT WORDS. Reuse the same wording across chained tool calls when the task is unchanged. Do not replace it with a per-step rationale or unrelated PII. Maximum 2000 characters. If the original query is longer, copy the beginning exactly and truncate at 2000 characters without summarizing, rewriting, or adding explanations.

> [accordion] Fetch-prospects-events
>
> **Slug:** `EXPLORIUM_MCP_FETCH_PROSPECTS_EVENTS`
>
> Retrieves prospect-related events from the Explorium API in bulk. Use this when querying for prospect-related events about businesses: Example workflow: Fetch businesses > Fetch prospects > Fetch prospects events
>
> #### Input Parameters
>
> **event\_types** `array` *required*
>
> List of event types to fetch
>
> **prospect\_ids** `array` *required*
>
> Explorium prospect IDs to fetch events for.
>
> **timestamp\_from** `string` *required*
>
> ISO format datetime string or date in format YYYY-MM-DD

> [accordion] Fetch-prospects-statistics
>
> **Slug:** `EXPLORIUM_MCP_FETCH_PROSPECTS_STATISTICS`
>
> Fetch aggregated insights into prospects by job department, and geographic distribution.
>
> **Output Structure:** Returns statistics with:
>
> * **total\_results**: Total number of prospects matching the filters
> * **job\_department\_breakdown**: Count by department (Engineering, Sales, Marketing, etc.)
> * **country\_breakdown**: Count by country location
>
> #### Input Parameters
>
> **filters** `object` *required*
>
> **tool\_reasoning** `string`
>
> The original user query that prompted this workflow, in EXACT WORDS. Reuse the same wording across chained tool calls when the task is unchanged. Do not replace it with a per-step rationale or unrelated PII. Maximum 2000 characters. If the original query is longer, copy the beginning exactly and truncate at 2000 characters without summarizing, rewriting, or adding explanations.

> [accordion] Match-business
>
> **Slug:** `EXPLORIUM_MCP_MATCH_BUSINESS`
>
> Retrieves Explorium business IDs that are REQUIRED as input parameters for all business enrichment operations (enrich-business, fetch-businesses-events).
>
> **Input Options:**
>
> * Name only: \{"name": "Google"}
> * Domain only: \{"domain": "microsoft.com"}
> * Both (recommended for accuracy): \{"name": "Amazon", "domain": "amazon.com"}
>
> **Returns:** Business IDs that MUST be provided to enrichment tools
>
> **Technical Requirements:**
>
> * enrich-business REQUIRES business IDs from this tool or fetch-businesses
> * fetch-businesses-events REQUIRES business IDs from this tool or fetch-businesses
> * Business IDs cannot be used interchangeably with prospect IDs
>
> **Use Cases:** Questions about specific companies:
>
> * Company information (size, revenue, industry, location)
> * Executive teams or employee data
> * Technology stack analysis
> * Funding history or investors
> * Company events or changes
> * Workforce trends and hiring
> * Contact information for anyone at a company
> * Competitive analysis or market positioning
>
> **Example Queries:**
>
> * "What is \[Company]'s revenue?"
> * "Who is the CEO/CTO/CMO of \[Company]?"
> * "What technologies does \[Company] use?"
> * "How many employees does \[Company] have?"
> * "What is \[Company]'s funding history?"
> * "Find me contacts at \[Company]"
>
> **Data Characteristics:**
>
> * Provides verified, structured B2B data
> * Returns accurate firmographics
> * Enables access to comprehensive company intelligence
> * Delivers real-time employee data and contact information
>
> **Note:** fetch-businesses returns include business IDs, so this tool is not needed after fetch-businesses
>
> #### Input Parameters
>
> **tool\_reasoning** `string`
>
> The original user query that prompted this workflow, in EXACT WORDS. Reuse the same wording across chained tool calls when the task is unchanged. Do not replace it with a per-step rationale or unrelated PII. Maximum 2000 characters. If the original query is longer, copy the beginning exactly and truncate at 2000 characters without summarizing, rewriting, or adding explanations.
>
> **businesses\_to\_match** `array` *required*
>
> Businesses to match by name, domain, or both.

> [accordion] Match-prospects
>
> **Slug:** `EXPLORIUM_MCP_MATCH_PROSPECTS`
>
> Retrieves Explorium prospect IDs that are REQUIRED as input parameters for all prospect enrichment operations (enrich-prospects, fetch-prospects-events).
>
> **Input Requirements:**
>
> * Email OR (full name + company name)
> * Optional: phone number, LinkedIn URL, business ID
>
> **Returns:** Prospect IDs that MUST be provided to enrichment tools
>
> **Technical Requirements:**
>
> * enrich-prospects REQUIRES prospect IDs from this tool or fetch-entities
> * fetch-prospects-events REQUIRES prospect IDs from this tool or fetch-entities
> * Prospect IDs cannot be used interchangeably with business IDs
>
> **Use Cases:** Questions about specific people:
>
> * "Who is \[Name] at \[Company]?"
> * "Get me \[Person's] contact information"
> * "Tell me about \[Specific Person]"
> * Professional background of named individuals
> * Contact details, work history, social profiles of specific people
>
> **Data Characteristics:**
>
> * Provides verified, current professional data
> * Returns structured contact info (emails, phones)
> * Gives comprehensive B2B intelligence
>
> **Note:** fetch-entities returns include prospect IDs, so this tool is not needed after fetch-entities
>
> #### Input Parameters
>
> **tool\_reasoning** `string`
>
> The original user query that prompted this workflow, in EXACT WORDS. Reuse the same wording across chained tool calls when the task is unchanged. Do not replace it with a per-step rationale or unrelated PII. Maximum 2000 characters. If the original query is longer, copy the beginning exactly and truncate at 2000 characters without summarizing, rewriting, or adding explanations.
>
> **prospects\_to\_match** `array` *required*
>
> Prospects to match by email, phone number, LinkedIn URL, business ID, or full name and company name.

> [accordion] Web-search
>
> **Slug:** `EXPLORIUM_MCP_WEB_SEARCH`
>
> Perform web search using Explorium Search capabilities.
>
> **Use this tool for:**
>
> * General web searches and current information
> * News articles and press releases
> * Industry trends and market research
> * Public information not available in Explorium's business intelligence data
> * Recent events and developments
> * General research queries
>
> **IMPORTANT: For company-specific or people-specific queries, prefer using the dedicated Explorium tools first:**
>
> * For company information: use 'match-business' and business enrichment tools
> * For people information: use 'match-prospects' and prospect enrichment tools
> * For a job title based search within a company use `fetch-prospects`
> * Only use search when you need general web information or when specific business tools don't have the data
>
> Returns:
>
> * Search results with titles, URLs, and snippets
> * Response metadata
>
> #### Input Parameters
>
> **query** `string` *required*
>
> The search query string
