Skip to main content
Glama
Meerkats-Ai

Hunter.io MCP Server

by Meerkats-Ai

hunter_find_email

Locate professional email addresses by providing a domain and individual details such as name or company. Ideal for targeted outreach and networking.

Instructions

Find an email address using domain and name information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNoThe name of the company
domainYesThe domain name of the company, e.g. "stripe.com"
first_nameNoThe first name of the person
full_nameNoThe full name of the person (alternative to first_name and last_name)
last_nameNoThe last name of the person

Implementation Reference

  • The handler logic for the 'hunter_find_email' tool, which validates input parameters using isFindEmailParams and calls the Hunter.io /email-finder API endpoint with retry logic.
    case 'hunter_find_email': {
      if (!isFindEmailParams(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid arguments for hunter_find_email'
        );
      }
    
      try {
        // Hunter.io API expects query parameters for email finder
        const response = await withRetry(
          async () => apiClient.get('/email-finder', { params: args }),
          'find email'
        );
    
        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,
        };
      }
    }
  • Input schema and metadata definition for the 'hunter_find_email' tool.
    const FIND_EMAIL_TOOL: Tool = {
      name: 'hunter_find_email',
      description: 'Find an email address using domain and name information.',
      inputSchema: {
        type: 'object',
        properties: {
          domain: {
            type: 'string',
            description: 'The domain name of the company, e.g. "stripe.com"',
          },
          first_name: {
            type: 'string',
            description: 'The first name of the person',
          },
          last_name: {
            type: 'string',
            description: 'The last name of the person',
          },
          company: {
            type: 'string',
            description: 'The name of the company',
          },
          full_name: {
            type: 'string',
            description: 'The full name of the person (alternative to first_name and last_name)',
          }
        },
        required: ['domain'],
      },
    };
  • src/index.ts:423-431 (registration)
    Registration of the 'hunter_find_email' tool (via FIND_EMAIL_TOOL) in the ListTools request handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        FIND_EMAIL_TOOL,
        VERIFY_EMAIL_TOOL,
        DOMAIN_SEARCH_TOOL,
        EMAIL_COUNT_TOOL,
        ACCOUNT_INFO_TOOL,
      ],
    }));
  • Type guard helper function to validate arguments for the 'hunter_find_email' tool.
    function isFindEmailParams(args: unknown): args is FindEmailParams {
      if (
        typeof args !== 'object' ||
        args === null ||
        !('domain' in args) ||
        typeof (args as { domain: unknown }).domain !== 'string'
      ) {
        return false;
      }
    
      // Optional parameters
      if (
        'first_name' in args &&
        (args as { first_name: unknown }).first_name !== undefined &&
        typeof (args as { first_name: unknown }).first_name !== 'string'
      ) {
        return false;
      }
    
      if (
        'last_name' in args &&
        (args as { last_name: unknown }).last_name !== undefined &&
        typeof (args as { last_name: unknown }).last_name !== 'string'
      ) {
        return false;
      }
    
      if (
        'company' in args &&
        (args as { company: unknown }).company !== undefined &&
        typeof (args as { company: unknown }).company !== 'string'
      ) {
        return false;
      }
    
      if (
        'full_name' in args &&
        (args as { full_name: unknown }).full_name !== undefined &&
        typeof (args as { full_name: unknown }).full_name !== 'string'
      ) {
        return false;
      }
    
      return true;
    }
  • TypeScript interface definition for parameters used by the 'hunter_find_email' tool.
    interface FindEmailParams {
      domain: string;
      first_name?: string;
      last_name?: string;
      company?: string;
      full_name?: string;
    }
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' an email address, implying a read-only operation, but doesn't address critical aspects like authentication requirements, rate limits, error handling, or what happens if no email is found. This is a significant gap for a tool with potential external API calls.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 (involving external data lookup), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the return format, potential errors, or behavioral traits like rate limits, which are crucial for effective tool invocation in a real-world context.

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?

The input schema has 100% description coverage, with clear parameter definitions (e.g., domain as 'The domain name of the company, e.g. "stripe.com"'). The description adds minimal value beyond the schema by mentioning 'domain and name information,' which aligns with parameters like 'first_name' and 'last_name,' but doesn't provide additional syntax or usage details. This meets the baseline 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 as 'Find an email address using domain and name information,' which specifies the verb (find), resource (email address), and key inputs (domain and name). However, it doesn't explicitly distinguish this tool from its siblings like 'hunter_domain_search' or 'hunter_verify_email,' which may also involve email-related searches, so it lacks sibling differentiation.

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 alternatives. It doesn't mention any prerequisites, exclusions, or comparisons to sibling tools such as 'hunter_domain_search' or 'hunter_verify_email,' leaving the agent without context for tool selection.

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