Skip to main content
Glama
Meerkats-Ai

Hunter.io MCP Server

by Meerkats-Ai

hunter_account_info

Retrieve detailed account information for managing and monitoring usage, limits, and configurations related to the Hunter.io API integration.

Instructions

Get information regarding your Hunter account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'hunter_account_info' tool within the CallToolRequestSchema switch statement. It validates parameters using isAccountInfoParams, calls the Hunter.io /account API with retry logic, and returns the account information as JSON or an error.
    case 'hunter_account_info': {
      if (!isAccountInfoParams(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid arguments for hunter_account_info'
        );
      }
    
      try {
        // Hunter.io API expects query parameters for account info
        const response = await withRetry(
          async () => apiClient.get('/account'),
          'account info'
        );
    
        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,
        };
      }
    }
  • The Tool schema definition for 'hunter_account_info', including name, description, and empty inputSchema since no parameters are required.
    const ACCOUNT_INFO_TOOL: Tool = {
      name: 'hunter_account_info',
      description: 'Get information regarding your Hunter account.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    };
  • src/index.ts:424-431 (registration)
    Registration of the 'hunter_account_info' tool (as ACCOUNT_INFO_TOOL) in the listTools response array.
      tools: [
        FIND_EMAIL_TOOL,
        VERIFY_EMAIL_TOOL,
        DOMAIN_SEARCH_TOOL,
        EMAIL_COUNT_TOOL,
        ACCOUNT_INFO_TOOL,
      ],
    }));
  • TypeScript interface defining the empty parameters for the hunter_account_info tool.
    interface AccountInfoParams {
      // No parameters needed
    }
  • Type guard function to validate arguments for the hunter_account_info tool, ensuring it's an object.
    function isAccountInfoParams(args: unknown): args is AccountInfoParams {
      return (
        typeof args === 'object' &&
        args !== null
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't specify what information is returned (e.g., account limits, usage stats, billing details), authentication requirements, rate limits, or error conditions. This is inadequate for a tool with zero annotation coverage.

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 states the core purpose without unnecessary words. It's appropriately sized for a simple tool and front-loaded with the essential action. Every word 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 simplicity (0 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what account information is returned, which is critical for an agent to understand the tool's utility. Without annotations or output schema, the description should provide more context about the return values.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no parameter documentation burden. The description doesn't need to compensate for missing param info. A baseline of 4 is appropriate since no parameters exist to explain.

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 action ('Get information') and resource ('your Hunter account'), making the purpose understandable. However, it doesn't differentiate this tool from its siblings (domain_search, email_count, etc.), which are all Hunter-related but serve different functions. A 5 would require explicit 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 like the sibling tools. It doesn't mention prerequisites, context for usage, or exclusions. While the purpose is clear, the lack of comparative guidance leaves the agent without direction on 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