Skip to main content
Glama
hunter-io

Hunter MCP Server

Official
by hunter-io

enrich_email

Retrieve comprehensive contact details from an email address, including name, location, and social profiles, to enhance lead data and verify identities.

Instructions

Return all the information associated with an email address, such as a person's name, location and social handles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYes

Implementation Reference

  • main.py:27-30 (handler)
    The main handler function that implements the logic for the 'enrich_email' tool by calling the Hunter API's 'people/find' endpoint with the provided email address.
    async def enrich_email(email: str) -> str:
        async with HunterAPIClient() as client:
            response = await client.get("people/find", {"email": email})
            return response
  • main.py:26-26 (registration)
    Registers the 'enrich_email' tool with the FastMCP server using the @mcp.tool decorator, including the tool description. The input schema is inferred from the function signature (email: str).
    @mcp.tool(description="Return all the information associated with an email address, such as a person's name, location and social handles.")
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. While it states what the tool returns, it doesn't disclose important behavioral traits such as rate limits, authentication requirements, data sources, accuracy considerations, privacy implications, or what happens when no information is found for an email address. The description is minimal and lacks operational context.

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 extremely concise - a single sentence that gets straight to the point. There's no wasted language or unnecessary elaboration. It's appropriately sized for a simple lookup tool with one parameter.

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 lack of annotations and output schema, the description is insufficiently complete. For an enrichment tool that presumably queries external data sources, the description should address data freshness, source reliability, privacy considerations, and what the return structure looks like. The single sentence description leaves too many operational questions unanswered.

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 description doesn't add any meaningful information about the single parameter beyond what's obvious from the parameter name 'email'. With 0% schema description coverage and only one parameter, the baseline would be 4, but the description fails to provide any additional context about email format requirements, validation, or examples that would be helpful for proper usage.

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: to return information associated with an email address, specifically mentioning person's name, location, and social handles. It uses a specific verb ('return') and resource ('information associated with an email address'), but doesn't explicitly distinguish from sibling tools like 'email_verifier' or 'email_finder'.

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. There are several sibling tools that might overlap (email_verifier, email_finder, domain_search), but the description doesn't indicate when enrich_email is appropriate versus these other tools, nor does it mention any prerequisites or constraints.

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/hunter-io/hunter-mcp'

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