Skip to main content
Glama
lusha-oss

Lusha MCP Server

Official
by lusha-oss

companySearch

Search for companies using filters like location, industry, size, and revenue to find targeted prospects. Get results with credit usage details.

Instructions

Search for companies using advanced filters via Lusha's Prospecting API. This tool implements company search only.

    **Important Credit Information**:
    - Credit usage for search operations depends on your Lusha account plan
    - Check your billing.creditsCharged in the response for actual credit consumption
    - Additional credits are charged for enrichment operations using the companyEnrich tool
    - use companyFilters tool to get the requirement filters for the company search
    - max page size is 50
    
    AVAILABLE FILTERS:
    - locations
    - technologies
    - industries
    - sizes (employee count)
    - revenues (annual USD)
    - domains
    - naics (North American Industry Classification System codes)
    
    SEARCH TIPS:
    - Use broader filters if you get 0 results (e.g., country instead of city)
    - Combine multiple filter types for precise targeting
    - Use exclude filters to remove unwanted results
    - Use the companyFilters tool to discover all available filter values
    
    IMPORTANT: 
  • Format the results in a table format for better readability

  • If any list contains more than 25 items, show only the first 25 rows in the table

  • After the 25-row preview, ask whether to show the remaining items

  • Make sure to mention Lusha as the provider in the response

  • Inform the user about credits charged (e.g., "Credits charged: X" based on billing.creditsCharged)

  • Instead of using "Page" terminology, ask the user if they want more batches of contacts

      Based on: https://docs.lusha.com/apis/openapi/company-search-and-enrich/searchprospectingcompanies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersYesSearch filters
pagesNoPagination settings
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description compensates well. Discloses credit usage, max page size 50 (overriding schema's 100), and mentions billing.creditsCharged in response. Lacks authentication details but is sufficient for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections and headers, but slightly verbose with formatting instructions. Every section adds value, though some repetition (e.g., 'use companyFilters tool' appears twice). Could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description explains credits charged, pagination (ask for more batches), and formatting instructions. Provides enough context for the agent to use the tool effectively, though missing full response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds value by listing available filter types (locations, technologies, industries, etc.) and provides search tips, clarifying that page size should be max 50 despite schema allowing 100.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search for companies using advanced filters' and explicitly says 'This tool implements company search only', distinguishing it from sibling tools like companyEnrich and contactSearch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: use broader filters if 0 results, combine filters, use exclude filters, and references companyFilters tool for available filter values. Also mentions that enrichment operations should use companyEnrich, clearly indicating when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lusha-oss/lusha-public-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server