Skip to main content
Glama
lusha-oss

Lusha MCP Server

Official
by lusha-oss

companyEnrich

Enrich company search results with detailed data using request IDs and company IDs. Provides comprehensive company information for selected companies.

Instructions

Get detailed company information from search results. WARNING: CHARGES CREDITS - always ask user first!

    REQUIREMENTS:
    - requestId: from prospectingCompany search response
    - companiesIds: array of company IDs (max 50)
    - User explicit consent required
    
    One credit charged per company enriched. Use only when user requests detailed information.
    
    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/enrichprospectingcompanies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestIdYesThe requestId from the Prospecting Search response
companiesIdsYesAn array of company IDs for enrichment. Min 1, max 50.
Behavior5/5

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

Describes credit charging per company, formatting (table, first 25 rows, batch requests), mentions Lusha as provider, and instructs to inform user about credits charged. No annotations exist, so description fully covers behavioral traits.

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-organized with sections and bullet points. Some redundancy in credit charging emphasis, but overall concise and actionable.

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

Completeness5/5

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

Comprehensive for a tool with no output schema: covers inputs, credit cost, formatting rules, preview limits, and references API documentation. No gaps for agent invocation.

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

Parameters3/5

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

Schema coverage is 100% with both parameters described. Description adds context (requestId from search response, companiesIds max 50) but largely repeats schema. Does not significantly enhance meaning beyond schema.

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?

Clearly states it enriches company information from search results, specifies required inputs (requestId, companiesIds) and limits (max 50). Distinguishes from sibling tools like companySearch and companyFilters.

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?

Explicitly warns about credit charges and requires user consent: 'WARNING: CHARGES CREDITS - always ask user first!' and 'Use only when user requests detailed information.' Provides clear when-to-use and prerequisite conditions.

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