Skip to main content
Glama
Meerkats-Ai

Hunter.io MCP Server

by Meerkats-Ai

hunter_domain_search

Locate email addresses associated with a specific domain or company name, with options to filter by type, limit results, and skip entries.

Instructions

Find all the email addresses corresponding to a website or company name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNoThe company name to search for (alternative to domain)
domainNoThe domain name to search for, e.g. "stripe.com"
limitNoThe maximum number of emails to return (default: 10, max: 100)
offsetNoThe number of emails to skip (default: 0)
typeNoThe type of emails to return (personal or generic)

Implementation Reference

  • The main execution logic for the 'hunter_domain_search' tool. Validates input using isDomainSearchParams, calls Hunter.io /domain-search API with retry logic, and returns the response or error.
    case 'hunter_domain_search': {
      if (!isDomainSearchParams(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid arguments for hunter_domain_search'
        );
      }
    
      try {
        // Hunter.io API expects query parameters for domain search
        const response = await withRetry(
          async () => apiClient.get('/domain-search', { params: args }),
          'domain search'
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response.data, null, 2),
            },
          ],
          isError: false,
        };
      } catch (error) {
        const errorMessage = axios.isAxiosError(error)
          ? `API Error: ${error.response?.data?.message || error.message}`
          : `Error: ${error instanceof Error ? error.message : String(error)}`;
    
        return {
          content: [{ type: 'text', text: errorMessage }],
          isError: true,
        };
      }
    }
  • Tool definition for 'hunter_domain_search' including name, description, and input schema specifying parameters like domain, company, limit, offset, and type.
    const DOMAIN_SEARCH_TOOL: Tool = {
      name: 'hunter_domain_search',
      description: 'Find all the email addresses corresponding to a website or company name.',
      inputSchema: {
        type: 'object',
        properties: {
          domain: {
            type: 'string',
            description: 'The domain name to search for, e.g. "stripe.com"',
          },
          company: {
            type: 'string',
            description: 'The company name to search for (alternative to domain)',
          },
          limit: {
            type: 'number',
            description: 'The maximum number of emails to return (default: 10, max: 100)',
          },
          offset: {
            type: 'number',
            description: 'The number of emails to skip (default: 0)',
          },
          type: {
            type: 'string',
            description: 'The type of emails to return (personal or generic)',
          }
        },
        required: [],
      },
    };
  • src/index.ts:424-431 (registration)
    Registers the 'hunter_domain_search' tool (as DOMAIN_SEARCH_TOOL) in the list of tools returned by the ListToolsRequestSchema handler.
      tools: [
        FIND_EMAIL_TOOL,
        VERIFY_EMAIL_TOOL,
        DOMAIN_SEARCH_TOOL,
        EMAIL_COUNT_TOOL,
        ACCOUNT_INFO_TOOL,
      ],
    }));
  • TypeScript interface defining the input parameters for the 'hunter_domain_search' tool.
    interface DomainSearchParams {
      domain?: string;
      company?: string;
      limit?: number;
      offset?: number;
      type?: string;
    }
  • Type guard function that validates if the provided arguments match the DomainSearchParams interface, used in the handler for input validation.
    function isDomainSearchParams(args: unknown): args is DomainSearchParams {
      if (
        typeof args !== 'object' ||
        args === null
      ) {
        return false;
      }
    
      // At least one of domain or company must be provided
      if (
        !('domain' in args || 'company' in args)
      ) {
        return false;
      }
    
      // Check domain if provided
      if (
        'domain' in args &&
        (args as { domain: unknown }).domain !== undefined &&
        typeof (args as { domain: unknown }).domain !== 'string'
      ) {
        return false;
      }
    
      // Check company if provided
      if (
        'company' in args &&
        (args as { company: unknown }).company !== undefined &&
        typeof (args as { company: unknown }).company !== 'string'
      ) {
        return false;
      }
    
      // Check limit if provided
      if (
        'limit' in args &&
        (args as { limit: unknown }).limit !== undefined &&
        typeof (args as { limit: unknown }).limit !== 'number'
      ) {
        return false;
      }
    
      // Check offset if provided
      if (
        'offset' in args &&
        (args as { offset: unknown }).offset !== undefined &&
        typeof (args as { offset: unknown }).offset !== 'number'
      ) {
        return false;
      }
    
      // Check type if provided
      if (
        'type' in args &&
        (args as { type: unknown }).type !== undefined &&
        typeof (args as { type: unknown }).type !== 'string'
      ) {
        return false;
      }
    
      return true;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'finds' email addresses, implying a read-only operation, but lacks details on permissions, rate limits, data sources (e.g., Hunter.io API), pagination (implied by limit/offset but not explained), or error handling. For a tool with 5 parameters and no annotations, this is a significant gap in transparency.

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

Conciseness5/5

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

The description is a single, efficient sentence: 'Find all the email addresses corresponding to a website or company name.' It's front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's complexity. Every part of the sentence earns its place.

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

Completeness2/5

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

Given the tool's complexity (5 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'find' entails (e.g., search results from a database), return format (list of emails with metadata?), or behavioral constraints. Without annotations or output schema, the agent lacks critical context for effective use.

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 description coverage is 100%, so the input schema fully documents all 5 parameters (company, domain, limit, offset, type) with descriptions. The description adds no additional parameter semantics beyond implying domain/company as alternatives, which is already covered in the schema. This meets the baseline of 3 for high schema coverage.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Find all the email addresses corresponding to a website or company name.' It specifies the verb ('find') and resource ('email addresses'), and distinguishes the input type (domain or company name) from siblings like hunter_find_email (which likely finds specific emails) or hunter_verify_email (which verifies emails). However, it doesn't explicitly differentiate from hunter_email_count (which might count emails without listing them), so it's not a perfect 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus its siblings. It doesn't mention alternatives like hunter_find_email for targeted searches or hunter_email_count for just counts, nor does it specify prerequisites or exclusions (e.g., when domain vs. company is preferred). This leaves the agent to infer usage from tool names alone, which is insufficient.

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

Related 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/Meerkats-Ai/hunter-io-mcp-server'

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