ai.explorium/mcp-explorium
autocomplete
Autocomplete values for business filters based on a query. Never use for fields not explicitly listed (e.g., `website_keywords`). Prefer `linkedin_category` over `google_category` when both apply. **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. **Category specificity check (`linkedin_category` vs `naics_category`):** When the user names a specific business type, the category you filter on must be as specific as the request — for ANY industry, not just common ones. 1. Run autocomplete with field=linkedin_category. This is the default route and normally the ONLY category autocomplete you make. 2. Test the best match: "Would a large share of companies in this category be something OTHER than what the user asked for?" - No → use linkedin_category. Done — do NOT also autocomplete naics_category. - Yes → the label is a parent industry that merely contains the request. Run autocomplete with field=naics_category and use the most specific matching NAICS code(s) instead. 3. Never run both category autocompletes as a routine double-check. The naics_category autocomplete is ONLY for when step 2 answers "Yes" or LinkedIn returned no plausible match. Exactly one of `linkedin_category` / `naics_category` per fetch — never both. **Category Selection Strategy:** When autocomplete returns multiple relevant categories, you MUST: - ✓ MUST include ALL applicable categories to maximize coverage - ✓ ALWAYS prioritize comprehensiveness over precision - ✗ ONLY exclude clearly unrelated categories - ✗ NEVER pad with broader parent categories when the user asked for a specific business type — trigger the NAICS fallback above instead - ✓ For broad queries → include more categories rather than fewer - VIOLATION: Limiting selection unnecessarily will reduce result quality **Session Storage:** - If session_id is provided, results will be stored for future reference - If not provided, a new session_id will be created and returned - Returns session_id in the response for future data retrieval Do NOT call autocomplete for: - `company_country_code`: List[str] — use valid ISO Alpha-2 country codes directly (e.g., "US", "IL") - `company_region_country_code`: List[str] — use valid ISO 3166-2 region codes directly (e.g., "US-NY", "IL-TA") - `prospect_country_code`: List[str] — use valid ISO Alpha-2 country codes directly (e.g., "US", "IL") - `prospect_region_country_code`: List[str] — use valid ISO 3166-2 region codes directly (e.g., "US-NY", "IL-TA") Hints: - Searching for SaaS? Use the keyword 'software'
Remote (network-hosted)
Other tools also called autocomplete?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"field": {
"enum": [
"naics_category",
"linkedin_category",
"company_tech_stack_tech",
"job_title",
"interests",
"skills",
"business_intent_topics",
"city_region"
],
"type": "string",
"description": "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": {
"type": "string",
"maxLength": 100,
"description": "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."
},
"session_id": {
"type": "string",
"pattern": "^session_[a-z0-9_]+$",
"description": "Session ID for tracking tool calls within the same user request context. CRITICAL RULES:\n- REUSE session_id when: refining, filtering, or continuing the SAME user request (narrowing down, adding criteria, or working with results from the current request)\n- CREATE NEW session (omit parameter) when: the user asks for something completely different (different company, different topic, separate unrelated request)\n- Session = all tool calls related to fulfilling one logical user request, including all refinements and follow-ups\n- Each distinct user request/topic = new session"
},
"tool_reasoning": {
"type": "string",
"maxLength": 2000,
"description": "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."
}
}
}